* [xen-unstable test] 27016: regressions - FAIL
@ 2014-06-09 13:09 xen.org
2014-06-10 9:02 ` Jan Beulich
0 siblings, 1 reply; 6+ messages in thread
From: xen.org @ 2014-06-09 13:09 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson
[-- Attachment #1: Type: text/plain, Size: 8142 bytes --]
flight 27016 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/27016/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-amd64 10 guest-saverestore fail REGR. vs. 26871
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-win7-amd64 7 windows-install fail pass in 26999
test-amd64-amd64-xl-sedf 11 guest-saverestore fail in 26999 pass in 27016
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt 9 guest-start fail never pass
test-amd64-amd64-libvirt 9 guest-start fail never pass
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-armhf-armhf-libvirt 9 guest-start fail never pass
test-armhf-armhf-xl 10 migrate-support-check fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop fail never pass
test-amd64-i386-xl-qemut-win7-amd64 14 guest-stop fail never pass
test-amd64-i386-xl-win7-amd64 14 guest-stop fail never pass
test-amd64-i386-xl-qemut-winxpsp3 14 guest-stop fail never pass
test-amd64-i386-xl-qemuu-winxpsp3 14 guest-stop fail never pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop fail never pass
test-amd64-i386-xl-qemuu-win7-amd64 14 guest-stop fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 14 guest-stop fail never pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop fail never pass
test-amd64-i386-xl-winxpsp3 14 guest-stop fail never pass
test-amd64-amd64-xl-winxpsp3 14 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 14 guest-stop fail never pass
test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop fail never pass
test-amd64-amd64-xl-win7-amd64 14 guest-stop fail in 26999 never pass
version targeted for testing:
xen 07884c98671a734f20f2ac8302032657d262f3c9
baseline version:
xen 7f8d8abcf6dfb85fae591a547b24f9b27d92272c
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Christian Wolter <wolter@b1-systems.de>
Christoph Egger <chegger@amazon.de>
David Zhuang <david.zhuang@oracle.com>
Fabio Fantoni <fabio.fantoni@m2r.biz>
Feng Wu <feng.wu@intel.com>
George Dunlap <george.dunlap@eu.citrix.com>
Ian Campbell <ian.campbell@citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
Jacek Konieczny <jajcus@jajcus.net>
Jan Beulich <jbeulich@suse.com>
Jason Andryuk <andryuk@aero.org>
Juergen Gross <jgross@suse.com>
Julien Grall <julien.grall@linaro.org>
Julien Grall<julien.grall@linaro.org>
Kevin Tian <kevin.tian@intel.com>
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Lai Jiangshan <laijs@cn.fujitsu.com>
Malcolm Crossley <malcolm.crossley@citrix.com>
Mukesh Rathor <mukesh.rathor@oracle.com>
Paul Durrant <paul.durrant@citrix.com>
Roger Pau Monné <roger.pau@citrix.com>
Tim Deegan <tim@xen.org>
Wen Congyang <wency@cn.fujitsu.com>
Yang Hongyang <yanghy@cn.fujitsu.com>
Yang Zhang <yang.z.zhang@intel.com>
Zhigang Wang <zhigang.x.wang@oracle.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
build-amd64-rumpuserxen pass
build-i386-rumpuserxen pass
test-amd64-amd64-xl pass
test-armhf-armhf-xl pass
test-amd64-i386-xl pass
test-amd64-i386-rhel6hvm-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 fail
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
test-amd64-amd64-rumpuserxen-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-win7-amd64 fail
test-amd64-i386-xl-win7-amd64 fail
test-amd64-i386-xl-credit2 pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-i386-rumpuserxen-i386 pass
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel pass
test-amd64-i386-qemut-rhel6hvm-intel pass
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-amd64-libvirt fail
test-armhf-armhf-libvirt fail
test-amd64-i386-libvirt fail
test-amd64-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-xl-sedf-pin pass
test-amd64-amd64-xl-sedf pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail
test-amd64-i386-xl-winxpsp3-vcpus1 fail
test-amd64-amd64-xl-qemut-winxpsp3 fail
test-amd64-i386-xl-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-amd64-i386-xl-qemuu-winxpsp3 fail
test-amd64-amd64-xl-winxpsp3 fail
test-amd64-i386-xl-winxpsp3 fail
------------------------------------------------------------
sg-report-flight on osstest.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images
Logs, config files, etc. are available at
http://www.chiark.greenend.org.uk/~xensrcts/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Not pushing.
(No revision log; it would be 985 lines long.)
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [xen-unstable test] 27016: regressions - FAIL
2014-06-09 13:09 [xen-unstable test] 27016: regressions - FAIL xen.org
@ 2014-06-10 9:02 ` Jan Beulich
2014-06-10 9:12 ` Ian Campbell
0 siblings, 1 reply; 6+ messages in thread
From: Jan Beulich @ 2014-06-10 9:02 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson
>>> On 09.06.14 at 15:09, <Ian.Jackson@eu.citrix.com> wrote:
> flight 27016 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/27016/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-freebsd10-amd64 10 guest-saverestore fail REGR. vs. 26871
>From the looks of it this failure is persistent (seen in all three flights
over the weekend), pointing at qemu and USB. Not sure who to
ask to look into this, not the least because none of the rather
many pending changes appear to be an immediate candidate.
Perhaps we ought to wait for the bisector to get going on it...
Jan
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [xen-unstable test] 27016: regressions - FAIL
2014-06-10 9:02 ` Jan Beulich
@ 2014-06-10 9:12 ` Ian Campbell
2014-06-10 10:55 ` Ian Jackson
0 siblings, 1 reply; 6+ messages in thread
From: Ian Campbell @ 2014-06-10 9:12 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel, ian.jackson
On Tue, 2014-06-10 at 10:02 +0100, Jan Beulich wrote:
> >>> On 09.06.14 at 15:09, <Ian.Jackson@eu.citrix.com> wrote:
> > flight 27016 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/27016/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-amd64-i386-freebsd10-amd64 10 guest-saverestore fail REGR. vs. 26871
>
> From the looks of it this failure is persistent (seen in all three flights
> over the weekend), pointing at qemu and USB. Not sure who to
> ask to look into this, not the least because none of the rather
> many pending changes appear to be an immediate candidate.
> Perhaps we ought to wait for the bisector to get going on it...
The bisector is close to fingering the big upstream qemu merge. Stefano
and Anthony are investigating and Ian J was looking into perhaps doing
an adhoc bisect of the upstream branch, but last I heard picking a
baseline was looking problematic.
This breakage made it through the qemu-upstream push gate because that
flight erroneously excluded the freebsd job. Ian has addressed this with
"make-flight: Do not filter the qemu-upstream-* jobs" but that doesn't
help us now (but will help next time).
Ian.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [xen-unstable test] 27016: regressions - FAIL
2014-06-10 9:12 ` Ian Campbell
@ 2014-06-10 10:55 ` Ian Jackson
2014-06-12 12:38 ` Ian Campbell
2014-06-12 15:45 ` Anthony PERARD
0 siblings, 2 replies; 6+ messages in thread
From: Ian Jackson @ 2014-06-10 10:55 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, Ian Campbell; +Cc: xen-devel, Jan Beulich
Ian Campbell writes ("Re: [Xen-devel] [xen-unstable test] 27016: regressions - FAIL"):
> On Tue, 2014-06-10 at 10:02 +0100, Jan Beulich wrote:
> > From the looks of it this failure is persistent (seen in all three flights
> > over the weekend), pointing at qemu and USB. Not sure who to
> > ask to look into this, not the least because none of the rather
> > many pending changes appear to be an immediate candidate.
> > Perhaps we ought to wait for the bisector to get going on it...
>
> The bisector is close to fingering the big upstream qemu merge. Stefano
> and Anthony are investigating and Ian J was looking into perhaps doing
> an adhoc bisect of the upstream branch, but last I heard picking a
> baseline was looking problematic.
Our options at this stage are:
* Continue to try to debug it, blocking other trees in the meantime.
* Force push xen-unstable (and other affected trees of which there
will probably be quite a few). That will turn this failure from a
blocking regression into an allowable failure. This will allow
other work to continue but may take the pressure off trying to fix
it.
* Revert the merge in qemu-upstream-unstable.git. This will return
us to qemu 1.6.0.
11:37 <anthonyper> Diziet, I did not find any obvious bug with qemu
2.0. All I found is the guest that take about 1 or
2 min to respond again
Stefano says that this is a decision for the release manager, and I'm
inclined to concur.
(If a force push is called for I will do it. I can also help with
reverting the merge if that's what's decided.)
Ian.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [xen-unstable test] 27016: regressions - FAIL
2014-06-10 10:55 ` Ian Jackson
@ 2014-06-12 12:38 ` Ian Campbell
2014-06-12 15:45 ` Anthony PERARD
1 sibling, 0 replies; 6+ messages in thread
From: Ian Campbell @ 2014-06-12 12:38 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel, Jan Beulich
Konrad, ping. This is awaiting a decision from you as release manager to
unblock staging I think.
On Tue, 2014-06-10 at 11:55 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [xen-unstable test] 27016: regressions - FAIL"):
> > On Tue, 2014-06-10 at 10:02 +0100, Jan Beulich wrote:
> > > From the looks of it this failure is persistent (seen in all three flights
> > > over the weekend), pointing at qemu and USB. Not sure who to
> > > ask to look into this, not the least because none of the rather
> > > many pending changes appear to be an immediate candidate.
> > > Perhaps we ought to wait for the bisector to get going on it...
> >
> > The bisector is close to fingering the big upstream qemu merge. Stefano
> > and Anthony are investigating and Ian J was looking into perhaps doing
> > an adhoc bisect of the upstream branch, but last I heard picking a
> > baseline was looking problematic.
>
> Our options at this stage are:
>
> * Continue to try to debug it, blocking other trees in the meantime.
>
> * Force push xen-unstable (and other affected trees of which there
> will probably be quite a few). That will turn this failure from a
> blocking regression into an allowable failure. This will allow
> other work to continue but may take the pressure off trying to fix
> it.
>
> * Revert the merge in qemu-upstream-unstable.git. This will return
> us to qemu 1.6.0.
>
> 11:37 <anthonyper> Diziet, I did not find any obvious bug with qemu
> 2.0. All I found is the guest that take about 1 or
> 2 min to respond again
>
> Stefano says that this is a decision for the release manager, and I'm
> inclined to concur.
>
> (If a force push is called for I will do it. I can also help with
> reverting the merge if that's what's decided.)
>
> Ian.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [xen-unstable test] 27016: regressions - FAIL
2014-06-10 10:55 ` Ian Jackson
2014-06-12 12:38 ` Ian Campbell
@ 2014-06-12 15:45 ` Anthony PERARD
1 sibling, 0 replies; 6+ messages in thread
From: Anthony PERARD @ 2014-06-12 15:45 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel, Stefano Stabellini, Ian Campbell, Jan Beulich
On Tue, Jun 10, 2014 at 11:55:09AM +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [xen-unstable test] 27016: regressions - FAIL"):
> > On Tue, 2014-06-10 at 10:02 +0100, Jan Beulich wrote:
> > > From the looks of it this failure is persistent (seen in all three flights
> > > over the weekend), pointing at qemu and USB. Not sure who to
> > > ask to look into this, not the least because none of the rather
> > > many pending changes appear to be an immediate candidate.
> > > Perhaps we ought to wait for the bisector to get going on it...
> >
> > The bisector is close to fingering the big upstream qemu merge. Stefano
> > and Anthony are investigating and Ian J was looking into perhaps doing
> > an adhoc bisect of the upstream branch, but last I heard picking a
> > baseline was looking problematic.
>
> Our options at this stage are:
>
> * Continue to try to debug it, blocking other trees in the meantime.
>
> * Force push xen-unstable (and other affected trees of which there
> will probably be quite a few). That will turn this failure from a
> blocking regression into an allowable failure. This will allow
> other work to continue but may take the pressure off trying to fix
> it.
>
> * Revert the merge in qemu-upstream-unstable.git. This will return
> us to qemu 1.6.0.
>
> 11:37 <anthonyper> Diziet, I did not find any obvious bug with qemu
> 2.0. All I found is the guest that take about 1 or
> 2 min to respond again
>
> Stefano says that this is a decision for the release manager, and I'm
> inclined to concur.
>
> (If a force push is called for I will do it. I can also help with
> reverting the merge if that's what's decided.)
The first qemu upstream commit to fail the test:
6eefccc0bb9c34051b1e21880fc3a1c1c8686edd
roms: update vgabios binaries
This also switches from lgplvgabios to seavgabios.
A more recent version of the seavgabios binary fix the issue with
freebsd, so I asked for a backport in an other email.
But there is still a minor issue related to qemu 2.0, it concernes VNC.
The screen does not properly get updated (when moving a window under
Windows for example).
--
Anthony PERARD
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-06-12 15:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-09 13:09 [xen-unstable test] 27016: regressions - FAIL xen.org
2014-06-10 9:02 ` Jan Beulich
2014-06-10 9:12 ` Ian Campbell
2014-06-10 10:55 ` Ian Jackson
2014-06-12 12:38 ` Ian Campbell
2014-06-12 15:45 ` Anthony PERARD
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.