* [xen-4.5-testing test] 58276: regressions - FAIL
@ 2015-06-10 3:28 osstest service user
2015-06-10 9:48 ` Jan Beulich
0 siblings, 1 reply; 3+ messages in thread
From: osstest service user @ 2015-06-10 3:28 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson
flight 58276 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58276/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-winxpsp3 15 guest-localmigrate/x10 fail REGR. vs. 57908
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-sedf 6 xen-boot fail REGR. vs. 57908
test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 57908
test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail like 57908
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 57908
test-armhf-armhf-libvirt 11 guest-start fail like 57908
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass
test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
test-amd64-i386-libvirt 12 migrate-support-check fail never pass
test-armhf-armhf-xl-arndale 12 migrate-support-check fail never pass
test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass
test-armhf-armhf-xl 12 migrate-support-check fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail never pass
test-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass
test-armhf-armhf-xl-sedf-pin 12 migrate-support-check fail never pass
test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass
version targeted for testing:
xen 5af278695f5c8b9e01f21803ec3afe40495e1716
baseline version:
xen 0f4362b43fbe2eb87b280f87c1ff89dff623bfdd
------------------------------------------------------------
People who touched revisions under test:
Ian Jackson <ian.jackson@eu.citrix.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-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-amd64-xl-pvh-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 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-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-rumpuserxen-i386 pass
test-amd64-amd64-xl-pvh-intel fail
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 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-xl-sedf-pin pass
test-armhf-armhf-xl-sedf-pin pass
test-amd64-amd64-xl-sedf pass
test-armhf-armhf-xl-sedf fail
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass
test-amd64-amd64-xl-qemut-winxpsp3 pass
test-amd64-i386-xl-qemut-winxpsp3 pass
test-amd64-amd64-xl-qemuu-winxpsp3 pass
test-amd64-i386-xl-qemuu-winxpsp3 fail
------------------------------------------------------------
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
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
commit 5af278695f5c8b9e01f21803ec3afe40495e1716
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date: Tue Jun 9 16:33:00 2015 +0100
QEMU_TAG update
(qemu changes not included)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [xen-4.5-testing test] 58276: regressions - FAIL
2015-06-10 3:28 [xen-4.5-testing test] 58276: regressions - FAIL osstest service user
@ 2015-06-10 9:48 ` Jan Beulich
2015-06-10 10:59 ` Ian Campbell
0 siblings, 1 reply; 3+ messages in thread
From: Jan Beulich @ 2015-06-10 9:48 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson, Stefano Stabellini
>>> On 10.06.15 at 05:28, <osstest@xenbits.xen.org> wrote:
> flight 58276 xen-4.5-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/58276/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-xl-qemuu-winxpsp3 15 guest-localmigrate/x10 fail REGR. vs. 57908
I just looked at this and ...
> Regressions which are regarded as allowable (not blocking):
> test-armhf-armhf-xl-sedf 6 xen-boot fail REGR. vs. 57908
> test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 57908
> test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail like 57908
... this another time: The former is on Intel, while the latter on AMD,
so unlikely (i.e. minus one of them being some random, unrelated
failure) to be host or even vendor specific. Since this test consists
of 10 migrations in a row, with guest liveliness only checked once at
the end, it's rather unlikely that we'll be able to tell anything from
looking at the logs taken at the end. Yet the guest not responding
to pings first of all raises the question of whether its interrupts are
somehow not arriving anymore as intended. Would it be possible to
look at such a guest in that final state to check whether e.g.
keyboard input / mouse movement still work? Or to take a series of
xenctx or xl vcpu-list outputs to see whether the guest is still doing
_something_ (i.e. not completely locked up)?
Also, has anyone with more tools/qemu/osstest knowledge than me
managed to gain at least some weak theory of where there might be
this qemuu dependency affecting _only_ the stable trees?
Jan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [xen-4.5-testing test] 58276: regressions - FAIL
2015-06-10 9:48 ` Jan Beulich
@ 2015-06-10 10:59 ` Ian Campbell
0 siblings, 0 replies; 3+ messages in thread
From: Ian Campbell @ 2015-06-10 10:59 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel, ian.jackson, Stefano Stabellini
On Wed, 2015-06-10 at 10:48 +0100, Jan Beulich wrote:
> >>> On 10.06.15 at 05:28, <osstest@xenbits.xen.org> wrote:
> > flight 58276 xen-4.5-testing real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/58276/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-amd64-i386-xl-qemuu-winxpsp3 15 guest-localmigrate/x10 fail REGR. vs. 57908
>
> I just looked at this and ...
>
> > Regressions which are regarded as allowable (not blocking):
> > test-armhf-armhf-xl-sedf 6 xen-boot fail REGR. vs. 57908
> > test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 57908
> > test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail like 57908
>
> ... this another time: The former is on Intel, while the latter on AMD,
> so unlikely (i.e. minus one of them being some random, unrelated
> failure) to be host or even vendor specific. Since this test consists
> of 10 migrations in a row, with guest liveliness only checked once at
> the end, it's rather unlikely that we'll be able to tell anything from
> looking at the logs taken at the end. Yet the guest not responding
> to pings first of all raises the question of whether its interrupts are
> somehow not arriving anymore as intended. Would it be possible to
> look at such a guest in that final state to check whether e.g.
> keyboard input / mouse movement still work? Or to take a series of
> xenctx or xl vcpu-list outputs to see whether the guest is still doing
> _something_ (i.e. not completely locked up)?
Osstest doesn't (AFAIK) have a mechanism for deciding to preserve a test
machine upon failure for later fiddling with.
The only choice would be to manually lock the machine and run adhoc
reproduction until the issue occurred.
>
> Also, has anyone with more tools/qemu/osstest knowledge than me
> managed to gain at least some weak theory of where there might be
> this qemuu dependency affecting _only_ the stable trees?
>
> Jan
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-06-10 11:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-10 3:28 [xen-4.5-testing test] 58276: regressions - FAIL osstest service user
2015-06-10 9:48 ` Jan Beulich
2015-06-10 10:59 ` Ian Campbell
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.