* [xen-4.6-testing test] 122657: regressions - FAIL
@ 2018-05-11 10:52 osstest service owner
2018-05-11 15:02 ` staging-4.6 seems to be broken Ian Jackson
0 siblings, 1 reply; 6+ messages in thread
From: osstest service owner @ 2018-05-11 10:52 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 122657 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122657/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-2 50 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 122461
test-amd64-i386-libvirt 18 guest-start/debian.repeat fail REGR. vs. 122461
test-amd64-i386-libvirt-xsm 18 guest-start/debian.repeat fail REGR. vs. 122461
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 16 guest-start/debianhvm.repeat fail REGR. vs. 122461
test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow 16 guest-localmigrate/x10 fail REGR. vs. 122461
test-amd64-i386-xl-qemuu-ovmf-amd64 18 guest-start/debianhvm.repeat fail REGR. vs. 122461
test-armhf-armhf-xl 12 guest-start fail REGR. vs. 122461
test-armhf-armhf-libvirt-xsm 16 guest-start/debian.repeat fail REGR. vs. 122461
test-armhf-armhf-libvirt 16 guest-start/debian.repeat fail REGR. vs. 122461
Tests which did not succeed, but are not blocking:
test-xtf-amd64-amd64-4 50 xtf/test-hvm64-lbr-tsx-vmentry fail like 122413
test-xtf-amd64-amd64-1 50 xtf/test-hvm64-lbr-tsx-vmentry fail like 122461
test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow 16 guest-localmigrate/x10 fail like 122461
test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 122461
test-armhf-armhf-xl-rtds 16 guest-start/debian.repeat fail like 122461
test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail like 122461
test-armhf-armhf-libvirt-xsm 14 saverestore-support-check fail like 122461
test-armhf-armhf-libvirt 14 saverestore-support-check fail like 122461
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 122461
test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 122461
test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 122461
test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail like 122461
test-xtf-amd64-amd64-1 37 xtf/test-hvm32pae-memop-seg fail never pass
test-xtf-amd64-amd64-1 52 xtf/test-hvm64-memop-seg fail never pass
test-xtf-amd64-amd64-1 76 xtf/test-pv32pae-xsa-194 fail never pass
test-xtf-amd64-amd64-5 37 xtf/test-hvm32pae-memop-seg fail never pass
test-xtf-amd64-amd64-2 37 xtf/test-hvm32pae-memop-seg fail never pass
test-xtf-amd64-amd64-4 37 xtf/test-hvm32pae-memop-seg fail never pass
test-xtf-amd64-amd64-5 52 xtf/test-hvm64-memop-seg fail never pass
test-xtf-amd64-amd64-4 52 xtf/test-hvm64-memop-seg fail never pass
test-xtf-amd64-amd64-2 52 xtf/test-hvm64-memop-seg fail never pass
test-xtf-amd64-amd64-5 76 xtf/test-pv32pae-xsa-194 fail never pass
test-xtf-amd64-amd64-2 76 xtf/test-pv32pae-xsa-194 fail never pass
test-xtf-amd64-amd64-4 76 xtf/test-pv32pae-xsa-194 fail never pass
test-xtf-amd64-amd64-3 37 xtf/test-hvm32pae-memop-seg fail never pass
test-xtf-amd64-amd64-3 52 xtf/test-hvm64-memop-seg fail never pass
test-amd64-i386-libvirt 13 migrate-support-check fail never pass
test-xtf-amd64-amd64-3 76 xtf/test-pv32pae-xsa-194 fail never pass
test-amd64-amd64-libvirt 13 migrate-support-check fail never pass
test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass
test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-armhf-armhf-xl-xsm 13 migrate-support-check fail never pass
test-armhf-armhf-xl-xsm 14 saverestore-support-check fail never pass
test-armhf-armhf-xl-credit2 13 migrate-support-check fail never pass
test-armhf-armhf-xl-credit2 14 saverestore-support-check fail never pass
test-armhf-armhf-xl-arndale 13 migrate-support-check fail never pass
test-armhf-armhf-xl-arndale 14 saverestore-support-check fail never pass
test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass
test-armhf-armhf-xl-multivcpu 13 migrate-support-check fail never pass
test-armhf-armhf-xl-multivcpu 14 saverestore-support-check fail never pass
test-armhf-armhf-xl-rtds 13 migrate-support-check fail never pass
test-armhf-armhf-xl-rtds 14 saverestore-support-check fail never pass
test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass
test-armhf-armhf-libvirt-xsm 13 migrate-support-check fail never pass
test-armhf-armhf-xl-cubietruck 13 migrate-support-check fail never pass
test-armhf-armhf-xl-cubietruck 14 saverestore-support-check fail never pass
test-armhf-armhf-libvirt 13 migrate-support-check fail never pass
test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass
test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail never pass
test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail never pass
test-armhf-armhf-xl-vhd 12 migrate-support-check fail never pass
test-armhf-armhf-xl-vhd 13 saverestore-support-check fail never pass
test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass
test-amd64-amd64-xl-qemut-win10-i386 10 windows-install fail never pass
test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass
version targeted for testing:
xen c53663a223ab3cd600855746673fe922fffb83e9
baseline version:
xen 927aca70011f83c44294f90275c18a0b3f7d7169
Last test of basis 122461 2018-04-27 07:57:51 Z 14 days
Testing same since 122657 2018-05-08 17:35:51 Z 2 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Jan Beulich <jbeulich@suse.com>
Roger Pau Monné <roger.pau@citrix.com>
Xen Project Security Team <security@xenproject.org>
jobs:
build-amd64-xsm pass
build-armhf-xsm pass
build-i386-xsm pass
build-amd64-xtf pass
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-prev pass
build-i386-prev pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
build-amd64-rumprun pass
build-i386-rumprun pass
test-xtf-amd64-amd64-1 pass
test-xtf-amd64-amd64-2 pass
test-xtf-amd64-amd64-3 pass
test-xtf-amd64-amd64-4 pass
test-xtf-amd64-amd64-5 pass
test-amd64-amd64-xl pass
test-armhf-armhf-xl fail
test-amd64-i386-xl pass
test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemut-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm fail
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-xsm pass
test-armhf-armhf-libvirt-xsm fail
test-amd64-i386-libvirt-xsm fail
test-amd64-amd64-xl-xsm pass
test-armhf-armhf-xl-xsm pass
test-amd64-i386-xl-xsm pass
test-amd64-amd64-qemuu-nested-amd fail
test-amd64-i386-qemut-rhel6hvm-amd pass
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemut-debianhvm-amd64 pass
test-amd64-i386-xl-qemut-debianhvm-amd64 pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-freebsd10-amd64 pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 fail
test-amd64-amd64-rumprun-amd64 pass
test-amd64-amd64-xl-qemut-win7-amd64 fail
test-amd64-i386-xl-qemut-win7-amd64 fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-qemut-ws16-amd64 fail
test-amd64-i386-xl-qemut-ws16-amd64 fail
test-amd64-amd64-xl-qemuu-ws16-amd64 fail
test-amd64-i386-xl-qemuu-ws16-amd64 fail
test-armhf-armhf-xl-arndale pass
test-amd64-amd64-xl-credit2 pass
test-armhf-armhf-xl-credit2 pass
test-armhf-armhf-xl-cubietruck pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-i386-rumprun-i386 pass
test-amd64-amd64-xl-qemut-win10-i386 fail
test-amd64-i386-xl-qemut-win10-i386 fail
test-amd64-amd64-xl-qemuu-win10-i386 fail
test-amd64-i386-xl-qemuu-win10-i386 fail
test-amd64-amd64-qemuu-nested-intel pass
test-amd64-i386-qemut-rhel6hvm-intel pass
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-amd64-libvirt pass
test-armhf-armhf-libvirt fail
test-amd64-i386-libvirt fail
test-amd64-amd64-migrupgrade pass
test-amd64-i386-migrupgrade pass
test-amd64-amd64-xl-multivcpu pass
test-armhf-armhf-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-libvirt-pair pass
test-amd64-i386-libvirt-pair pass
test-amd64-amd64-amd64-pvgrub pass
test-amd64-amd64-i386-pvgrub pass
test-amd64-amd64-pygrub pass
test-amd64-amd64-xl-qcow2 pass
test-armhf-armhf-libvirt-raw pass
test-amd64-i386-xl-raw pass
test-amd64-amd64-xl-rtds pass
test-armhf-armhf-xl-rtds fail
test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow fail
test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow fail
test-amd64-amd64-xl-shadow pass
test-amd64-i386-xl-shadow pass
test-amd64-amd64-libvirt-vhd pass
test-armhf-armhf-xl-vhd pass
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
commit c53663a223ab3cd600855746673fe922fffb83e9
Author: Jan Beulich <jbeulich@suse.com>
Date: Tue May 8 18:28:20 2018 +0100
x86/HVM: guard against emulator driving ioreq state in weird ways
In the case where hvm_wait_for_io() calls wait_on_xen_event_channel(),
p->state ends up being read twice in succession: once to determine that
state != p->state, and then again at the top of the loop. This gives a
compromised emulator a chance to change the state back between the two
reads, potentially keeping Xen in a loop indefinitely.
Instead:
* Read p->state once in each of the wait_on_xen_event_channel() tests,
* re-use that value the next time around,
* and insist that the states continue to transition "forward" (with the
exception of the transition to STATE_IOREQ_NONE).
This is XSA-262.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: George Dunlap <george.dunlap@citrix.com>
commit c5339c594708468310564784159e8f982241d702
Author: Xen Project Security Team <security@xenproject.org>
Date: Mon Apr 23 16:56:47 2018 +0100
x86/vpt: add support for IO-APIC routed interrupts
And modify the HPET code to make use of it. Currently HPET interrupts
are always treated as ISA and thus injected through the vPIC. This is
wrong because HPET interrupts when not in legacy mode should be
injected from the IO-APIC.
To make things worse, the supported interrupt routing values are set
to [20..23], which clearly falls outside of the ISA range, thus
leading to an ASSERT in debug builds or memory corruption in non-debug
builds because the interrupt injection code will write out of the
bounds of the arch.hvm_domain.vpic array.
Since the HPET interrupt source can change between ISA and IO-APIC
always destroy the timer before changing the mode, or else Xen risks
changing it while the timer is active.
Note that vpt interrupt injection is racy in the sense that the
vIO-APIC RTE entry can be written by the guest in between the call to
pt_irq_masked and hvm_ioapic_assert, or the call to pt_update_irq and
pt_intr_post. Those are not deemed to be security issues, but rather
quirks of the current implementation. In the worse case the guest
might lose interrupts or get multiple interrupt vectors injected for
the same timer source.
This is part of XSA-261.
Address actual and potential compiler warnings. Fix formatting.
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
commit 3b9667632d52995bdf576e627bc8ea994d6941ee
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Tue May 8 18:28:03 2018 +0100
x86/traps: Fix handling of #DB exceptions in hypervisor context
The WARN_ON() can be triggered by guest activities, and emits a full stack
trace without rate limiting. Swap it out for a ratelimited printk with just
enough information to work out what is going on.
Not all #DB exceptions are traps, so blindly continuing is not a safe action
to take. We don't let PV guests select these settings in the real %dr7 to
begin with, but for added safety against unexpected situations, detect the
fault cases and crash in an obvious manner.
This is part of XSA-260 / CVE-2018-8897.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
commit 2f3cde33049e159b334cbdbea4e59a486138edea
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Tue May 8 18:28:03 2018 +0100
x86/traps: Use an Interrupt Stack Table for #DB
PV guests can use architectural corner cases to cause #DB to be raised after
transitioning into supervisor mode.
Use an interrupt stack table for #DB to prevent the exception being taken with
a guest controlled stack pointer.
This is part of XSA-260 / CVE-2018-8897.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
commit acd86611dc7d2cf8fc9ff66067341f3591ad31fe
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Tue May 8 18:28:03 2018 +0100
x86/pv: Move exception injection into {,compat_}test_all_events()
This allows paths to jump straight to {,compat_}test_all_events() and have
injection of pending exceptions happen automatically, rather than requiring
all calling paths to handle exceptions themselves.
The normal exception path is simplified as a result, and
compat_post_handle_exception() is removed entirely.
This is part of XSA-260 / CVE-2018-8897.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
commit 5ddc3f83b4beb02eb8227dc938888d30760272c3
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Tue May 8 18:28:03 2018 +0100
x86/traps: Fix %dr6 handing in #DB handler
Most bits in %dr6 accumulate, rather than being set directly based on the
current source of #DB. Have the handler follow the manuals guidance, which
avoids leaking hypervisor debugging activities into guest context.
This is part of XSA-260 / CVE-2018-8897.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* staging-4.6 seems to be broken
2018-05-11 10:52 [xen-4.6-testing test] 122657: regressions - FAIL osstest service owner
@ 2018-05-11 15:02 ` Ian Jackson
2018-05-14 13:40 ` Jan Beulich
0 siblings, 1 reply; 6+ messages in thread
From: Ian Jackson @ 2018-05-11 15:02 UTC (permalink / raw)
To: xen-devel; +Cc: Andrew Cooper, Jan Beulich, Roger Pau Monné
osstest service owner writes ("[xen-4.6-testing test] 122657: regressions - FAIL"):
> flight 122657 xen-4.6-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/122657/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-xtf-amd64-amd64-2 50 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 122461
> test-amd64-i386-libvirt 18 guest-start/debian.repeat fail REGR. vs. 122461
> test-amd64-i386-libvirt-xsm 18 guest-start/debian.repeat fail REGR. vs. 122461
> test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 16 guest-start/debianhvm.repeat fail REGR. vs. 122461
> test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow 16 guest-localmigrate/x10 fail REGR. vs. 122461
> test-amd64-i386-xl-qemuu-ovmf-amd64 18 guest-start/debianhvm.repeat fail REGR. vs. 122461
At least some of these are surely real regressions.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: staging-4.6 seems to be broken
2018-05-11 15:02 ` staging-4.6 seems to be broken Ian Jackson
@ 2018-05-14 13:40 ` Jan Beulich
2018-05-14 13:46 ` Ian Jackson
0 siblings, 1 reply; 6+ messages in thread
From: Jan Beulich @ 2018-05-14 13:40 UTC (permalink / raw)
To: Ian Jackson; +Cc: Andrew Cooper, xen-devel, Roger Pau Monne
>>> On 11.05.18 at 17:02, <ian.jackson@citrix.com> wrote:
> osstest service owner writes ("[xen-4.6-testing test] 122657: regressions -
> FAIL"):
>> flight 122657 xen-4.6-testing real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/122657/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> test-xtf-amd64-amd64-2 50 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 122461
>> test-amd64-i386-libvirt 18 guest-start/debian.repeat fail REGR. vs. 122461
>> test-amd64-i386-libvirt-xsm 18 guest-start/debian.repeat fail REGR. vs. 122461
>> test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 16 guest-start/debianhvm.repeat fail REGR. vs. 122461
>> test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow 16 guest-localmigrate/x10 fail REGR. vs. 122461
>> test-amd64-i386-xl-qemuu-ovmf-amd64 18 guest-start/debianhvm.repeat fail REGR. vs. 122461
>
> At least some of these are surely real regressions.
Are you saying that just because of the amount of failures above, or
because of some observations from log files or alike? I'm asking because
122699 looks quite a bit better.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: staging-4.6 seems to be broken
2018-05-14 13:40 ` Jan Beulich
@ 2018-05-14 13:46 ` Ian Jackson
2018-05-14 14:06 ` Jan Beulich
0 siblings, 1 reply; 6+ messages in thread
From: Ian Jackson @ 2018-05-14 13:46 UTC (permalink / raw)
To: Jan Beulich; +Cc: Andrew Cooper, xen-devel, Roger Pau Monne
Jan Beulich writes ("Re: staging-4.6 seems to be broken"):
> On 11.05.18 at 17:02, <ian.jackson@citrix.com> wrote:
> > osstest service owner writes ("[xen-4.6-testing test] 122657: regressions -
...
> > At least some of these are surely real regressions.
>
> Are you saying that just because of the amount of failures above, or
> because of some observations from log files or alike? I'm asking because
> 122699 looks quite a bit better.
The former.
And yes, 122699 does look better. This is concerning. I wonder what
the trouble can have been with 122657.
There have been a number of problems with some test hosts (which are
causing lots of fallout), but that's not what's wrong with 122657.
Hrrrm.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: staging-4.6 seems to be broken
2018-05-14 13:46 ` Ian Jackson
@ 2018-05-14 14:06 ` Jan Beulich
2018-05-14 14:24 ` Ian Jackson
0 siblings, 1 reply; 6+ messages in thread
From: Jan Beulich @ 2018-05-14 14:06 UTC (permalink / raw)
To: Ian Jackson; +Cc: Andrew Cooper, xen-devel, Roger Pau Monne
>>> On 14.05.18 at 15:46, <ian.jackson@citrix.com> wrote:
> Jan Beulich writes ("Re: staging-4.6 seems to be broken"):
>> On 11.05.18 at 17:02, <ian.jackson@citrix.com> wrote:
>> > osstest service owner writes ("[xen-4.6-testing test] 122657: regressions -
> ...
>> > At least some of these are surely real regressions.
>>
>> Are you saying that just because of the amount of failures above, or
>> because of some observations from log files or alike? I'm asking because
>> 122699 looks quite a bit better.
>
> The former.
>
> And yes, 122699 does look better. This is concerning. I wonder what
> the trouble can have been with 122657.
>
> There have been a number of problems with some test hosts (which are
> causing lots of fallout), but that's not what's wrong with 122657.
>
> Hrrrm.
Hrrrm indeed. 4.8 flight 12658 and 4.9 flight 12659 look about as bad as
the 4.6 one you've commented on.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: staging-4.6 seems to be broken
2018-05-14 14:06 ` Jan Beulich
@ 2018-05-14 14:24 ` Ian Jackson
0 siblings, 0 replies; 6+ messages in thread
From: Ian Jackson @ 2018-05-14 14:24 UTC (permalink / raw)
To: Jan Beulich; +Cc: Andrew Cooper, xen-devel, Roger Pau Monne
Jan Beulich writes ("Re: staging-4.6 seems to be broken"):
> Hrrrm indeed. 4.8 flight 12658 and 4.9 flight 12659 look about as bad as
> the 4.6 one you've commented on.
I took a look at the host histories for some of the hosts involved and
these failures do not seem to have occurred at the same time.
So whatever it is, it is not a transient general infrastructure
failure. It moves about from one branch to another, one host to
another and one time to another. Maybe corrupted builds are involved.
I guess I'm hoping that things will improve now that I have taken out
two more broken or flaky machines.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-05-14 14:24 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-11 10:52 [xen-4.6-testing test] 122657: regressions - FAIL osstest service owner
2018-05-11 15:02 ` staging-4.6 seems to be broken Ian Jackson
2018-05-14 13:40 ` Jan Beulich
2018-05-14 13:46 ` Ian Jackson
2018-05-14 14:06 ` Jan Beulich
2018-05-14 14:24 ` Ian Jackson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.