* [xen-unstable test] 123831: trouble: broken/fail/pass
@ 2018-06-07 1:55 osstest service owner
2018-06-07 5:39 ` Juergen Gross
0 siblings, 1 reply; 6+ messages in thread
From: osstest service owner @ 2018-06-07 1:55 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 123831 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/123831/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumprun-i386 <job status> broken
test-amd64-i386-rumprun-i386 4 host-install(4) broken REGR. vs. 123799
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail like 123799
test-armhf-armhf-libvirt 14 saverestore-support-check fail like 123799
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 123799
test-armhf-armhf-libvirt-xsm 14 saverestore-support-check fail like 123799
test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 123799
test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 123799
test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 123799
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail like 123799
test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail like 123799
test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 123799
test-amd64-i386-xl-pvshim 12 guest-start fail never pass
test-amd64-i386-libvirt 13 migrate-support-check fail never pass
test-arm64-arm64-xl-credit2 13 migrate-support-check fail never pass
test-arm64-arm64-xl-credit2 14 saverestore-support-check fail never pass
test-amd64-i386-libvirt-xsm 13 migrate-support-check 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-arm64-arm64-xl-xsm 13 migrate-support-check fail never pass
test-arm64-arm64-libvirt-xsm 13 migrate-support-check fail never pass
test-arm64-arm64-libvirt-xsm 14 saverestore-support-check fail never pass
test-arm64-arm64-xl-xsm 14 saverestore-support-check fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-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-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass
test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass
test-armhf-armhf-xl 13 migrate-support-check fail never pass
test-armhf-armhf-xl 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-armhf-armhf-libvirt 13 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-libvirt-xsm 13 migrate-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-multivcpu 13 migrate-support-check fail never pass
test-armhf-armhf-xl-multivcpu 14 saverestore-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-arm64-arm64-xl 13 migrate-support-check fail never pass
test-arm64-arm64-xl 14 saverestore-support-check 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-ws16-amd64 17 guest-stop fail never pass
test-armhf-armhf-libvirt-raw 12 migrate-support-check 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
test-amd64-amd64-xl-qemut-win10-i386 10 windows-install fail never pass
test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass
version targeted for testing:
xen 3960f3a52346348e6b0306f65d19375612bd35b9
baseline version:
xen 06f542f8f2e446c01bd0edab51e9450af7f6e05b
Last test of basis 123799 2018-06-04 11:02:20 Z 2 days
Testing same since 123831 2018-06-05 20:29:59 Z 1 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Christian Lindig <christian.lindig@citrix.com>
Marcello Seri <marcello.seri@citrix.com>
jobs:
build-amd64-xsm pass
build-arm64-xsm pass
build-armhf-xsm pass
build-i386-xsm pass
build-amd64-xtf pass
build-amd64 pass
build-arm64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-arm64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-prev pass
build-i386-prev pass
build-amd64-pvops pass
build-arm64-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-arm64-arm64-xl pass
test-armhf-armhf-xl pass
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 pass
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-arm64-arm64-libvirt-xsm pass
test-armhf-armhf-libvirt-xsm pass
test-amd64-i386-libvirt-xsm pass
test-amd64-amd64-xl-xsm pass
test-arm64-arm64-xl-xsm pass
test-armhf-armhf-xl-xsm pass
test-amd64-i386-xl-xsm pass
test-amd64-amd64-qemuu-nested-amd fail
test-amd64-amd64-xl-pvhv2-amd pass
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 pass
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-arm64-arm64-xl-credit2 pass
test-armhf-armhf-xl-credit2 pass
test-armhf-armhf-xl-cubietruck pass
test-amd64-amd64-examine pass
test-arm64-arm64-examine pass
test-armhf-armhf-examine pass
test-amd64-i386-examine pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-i386-rumprun-i386 broken
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-amd64-xl-pvhv2-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 pass
test-amd64-i386-libvirt pass
test-amd64-amd64-livepatch pass
test-amd64-i386-livepatch pass
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-xl-pvshim pass
test-amd64-i386-xl-pvshim fail
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 pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow pass
test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow pass
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
broken-job test-amd64-i386-rumprun-i386 broken
broken-step test-amd64-i386-rumprun-i386 host-install(4)
Not pushing.
------------------------------------------------------------
commit 3960f3a52346348e6b0306f65d19375612bd35b9
Author: Marcello Seri <marcello.seri@citrix.com>
Date: Thu May 31 14:05:37 2018 +0100
ocaml/xenstored: reduce use of unsafe conversions
The rationalisation of the Xs_ring interface in the xb library
allows to further reduce the unsafe calls withouth introducing
copies. This patch also contains some further code cleanups.
Signed-off-by: Marcello Seri <marcello.seri@citrix.com>
Acked-by: Christian Lindig <christian.lindig@citrix.com>
Tested-by: Andrew Cooper <andrew.cooper3@citrix.com>
Release-acked-by: Juergen Gross <jgross@suse.com>
commit ec7d54dd1a87801ed328f4fa38ffdeaef1265958
Author: Marcello Seri <marcello.seri@citrix.com>
Date: Thu May 31 14:05:36 2018 +0100
ocaml/libs/xb: Use bytes in place of strings for mutable buffers
Since Ocaml 4.06.0, that made safe-string on by default, the compiler is
allowed to perform optimisations on immutable strings. They should no
longer be used as mutable buffers, and bytes should be used instead.
The C stubs for Xs_ring have been updated to use bytes, and the interface
rationalised mimicking the new Unix module in the standard library (the
implementation of Unix.write_substring uses unsafe_of_string in the exact same
way, and both the write implementations are using the bytes as an immutable
payload for the write).
Signed-off-by: Marcello Seri <marcello.seri@citrix.com>
Acked-by: Christian Lindig <christian.lindig@citrix.com>
Tested-by: Andrew Cooper <andrew.cooper3@citrix.com>
Release-acked-by: Juergen Gross <jgross@suse.com>
commit 237c31b5a1d5aa88cdb59b8c31b1b62eb13e82d1
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Fri Jun 1 14:08:59 2018 +0100
x86/traps: Fix error handling of the pv %dr7 shadow state
c/s "x86/pv: Introduce and use x86emul_write_dr()" fixed a bug with IO shadow
handling, in that it remained stale and visible until %dr7.L/G got set again.
However, it neglected the -EPERM return inbetween these two hunks, introducing
a different bug in which a write to %dr7 which tries to set IO breakpoints
without %cr4.DE being set clobbers the IO state, rather than leaves it alone.
Instead, move the zeroing slightly later, which guarentees that the shadow
gets written exactly once, on a successful update to %dr7.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
Release-acked-by: Juergen Gross <jgross@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
* Re: [xen-unstable test] 123831: trouble: broken/fail/pass
2018-06-07 1:55 [xen-unstable test] 123831: trouble: broken/fail/pass osstest service owner
@ 2018-06-07 5:39 ` Juergen Gross
2018-06-07 10:29 ` Ian Jackson
0 siblings, 1 reply; 6+ messages in thread
From: Juergen Gross @ 2018-06-07 5:39 UTC (permalink / raw)
To: osstest service owner, xen-devel; +Cc: Andrew Cooper, Ian Jackson
On 07/06/18 03:55, osstest service owner wrote:
> flight 123831 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/123831/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-rumprun-i386 <job status> broken
> test-amd64-i386-rumprun-i386 4 host-install(4) broken REGR. vs. 123799
The same host (italia1) that had the failed xtf test yesterday. The two
failures are looking very similar to me.
Again the question: should we do a force push?
Juergen
_______________________________________________
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: [xen-unstable test] 123831: trouble: broken/fail/pass
2018-06-07 5:39 ` Juergen Gross
@ 2018-06-07 10:29 ` Ian Jackson
2018-06-07 11:33 ` Juergen Gross
0 siblings, 1 reply; 6+ messages in thread
From: Ian Jackson @ 2018-06-07 10:29 UTC (permalink / raw)
To: Juergen Gross; +Cc: xen-devel, Andrew Cooper
Juergen Gross writes ("Re: [Xen-devel] [xen-unstable test] 123831: trouble: broken/fail/pass"):
> The same host (italia1) that had the failed xtf test yesterday. The two
> failures are looking very similar to me.
>
> Again the question: should we do a force push?
I think the final decision is up to you, but I would reason along
these lines:
The point of the push gate is to stop regressions making it into
master. However, osstest cannot currently handle heisenbugs well, so
it punts: when something is identified as a heisenbug, it is not
considered a regression.
There is this failure in 123831
(3960f3a52346348e6b0306f65d19375612bd35b9, staging)
test-xtf-amd64-amd64-5 <job status> broken
test-xtf-amd64-amd64-5 4 host-install(4) broken pass in 123670
This is an infrastructure problem. It means that that xtf test didn't
run. However, each flight runs the same battery of tests on 5
different hosts; so identical tests were run on other hosts. We're
just missing 20% of the XTF test host diversity we would have had.
So on that basis a force push is justified, because we can see that
the failure in 123831 does not really give any reason to suspect a
regression and the test coverage was only slightly reduced compared to
what was planned.
However, there are these failures in 123799
(06f542f8f2e446c01bd0edab51e9450af7f6e05b, master)
test-armhf-armhf-xl-arndale
5 host-ping-check-native fail
REGR. vs. 123323
This is very likely the known arndale bug and not a cause for concern.
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm
14 guest-saverestore.2 fail
REGR. vs. 123323b
This failure is being discussed in email. Obviously this is not a
regression from master, since it's *in* master. But it might be a
release critical bug.
If it is a release critical bug then branching (and consequently
opening staging again) might entrench the bug, both by allowing
effort to go to "shiny new stuff", and by making it harder to fix as
staging diverges from staging-4.11.
So I think overall, I would say this justifies a force push but if the
reason for wanting a force push was to enable branching, there is an
actual decision to be made, which is a matter of judgement.
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: [xen-unstable test] 123831: trouble: broken/fail/pass
2018-06-07 10:29 ` Ian Jackson
@ 2018-06-07 11:33 ` Juergen Gross
2018-06-07 11:58 ` Ian Jackson
0 siblings, 1 reply; 6+ messages in thread
From: Juergen Gross @ 2018-06-07 11:33 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel, Andrew Cooper
On 07/06/18 12:29, Ian Jackson wrote:
> Juergen Gross writes ("Re: [Xen-devel] [xen-unstable test] 123831: trouble: broken/fail/pass"):
>> The same host (italia1) that had the failed xtf test yesterday. The two
>> failures are looking very similar to me.
>>
>> Again the question: should we do a force push?
>
> I think the final decision is up to you, but I would reason along
> these lines:
>
> The point of the push gate is to stop regressions making it into
> master. However, osstest cannot currently handle heisenbugs well, so
> it punts: when something is identified as a heisenbug, it is not
> considered a regression.
>
>
> There is this failure in 123831
> (3960f3a52346348e6b0306f65d19375612bd35b9, staging)
>
> test-xtf-amd64-amd64-5 <job status> broken
> test-xtf-amd64-amd64-5 4 host-install(4) broken pass in 123670
>
> This is an infrastructure problem. It means that that xtf test didn't
> run. However, each flight runs the same battery of tests on 5
> different hosts; so identical tests were run on other hosts. We're
> just missing 20% of the XTF test host diversity we would have had.
>
> So on that basis a force push is justified, because we can see that
> the failure in 123831 does not really give any reason to suspect a
> regression and the test coverage was only slightly reduced compared to
> what was planned.
>
>
> However, there are these failures in 123799
> (06f542f8f2e446c01bd0edab51e9450af7f6e05b, master)
>
> test-armhf-armhf-xl-arndale
> 5 host-ping-check-native fail
> REGR. vs. 123323
>
> This is very likely the known arndale bug and not a cause for concern.
>
> test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm
> 14 guest-saverestore.2 fail
> REGR. vs. 123323b
>
> This failure is being discussed in email. Obviously this is not a
> regression from master, since it's *in* master. But it might be a
> release critical bug.
I'm quite sure it is. OTOH I suspect it should have been addressed
in 4.10 already...
Thinking more about it I believe this is the right time to try
fixing that bug. In case there is no objection I'd like to declare it
as being release critical.
> If it is a release critical bug then branching (and consequently
> opening staging again) might entrench the bug, both by allowing
> effort to go to "shiny new stuff", and by making it harder to fix as
> staging diverges from staging-4.11.
Right.
> So I think overall, I would say this justifies a force push but if the
> reason for wanting a force push was to enable branching, there is an
> actual decision to be made, which is a matter of judgement.
Thanks for the detailed answer, which is more or less following the same
line of thoughts I've had.
So lets wait and see whether there is progress catching the domain save
bug.
Are you fine then to lift the current commit moratorium?
Juergen
_______________________________________________
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: [xen-unstable test] 123831: trouble: broken/fail/pass
2018-06-07 11:33 ` Juergen Gross
@ 2018-06-07 11:58 ` Ian Jackson
2018-06-07 12:21 ` Juergen Gross
0 siblings, 1 reply; 6+ messages in thread
From: Ian Jackson @ 2018-06-07 11:58 UTC (permalink / raw)
To: Juergen Gross; +Cc: xen-devel, Andrew Cooper
Juergen Gross writes ("Re: [Xen-devel] [xen-unstable test] 123831: trouble: broken/fail/pass"):
> Are you fine then to lift the current commit moratorium?
That seems sensible, if you don't expect to be trying to branch RSN
because of the save/restore bug.
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: [xen-unstable test] 123831: trouble: broken/fail/pass
2018-06-07 11:58 ` Ian Jackson
@ 2018-06-07 12:21 ` Juergen Gross
0 siblings, 0 replies; 6+ messages in thread
From: Juergen Gross @ 2018-06-07 12:21 UTC (permalink / raw)
To: Ian Jackson, committers; +Cc: xen-devel, Andrew Cooper
On 07/06/18 13:58, Ian Jackson wrote:
> Juergen Gross writes ("Re: [Xen-devel] [xen-unstable test] 123831: trouble: broken/fail/pass"):
>> Are you fine then to lift the current commit moratorium?
>
> That seems sensible, if you don't expect to be trying to branch RSN
> because of the save/restore bug.
Okay, committers, you can commit release-acked patches again.
Juergen
_______________________________________________
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-06-07 12:21 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-07 1:55 [xen-unstable test] 123831: trouble: broken/fail/pass osstest service owner
2018-06-07 5:39 ` Juergen Gross
2018-06-07 10:29 ` Ian Jackson
2018-06-07 11:33 ` Juergen Gross
2018-06-07 11:58 ` Ian Jackson
2018-06-07 12:21 ` Juergen Gross
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.