xen.org
2013-Mar-08 13:40 UTC
[xen-unstable test] 17180: regressions - trouble: broken/fail/pass
flight 17180 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/17180/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-credit2 5 xen-boot fail REGR. vs. 16772
test-amd64-i386-pv 3 host-install(3) broken REGR. vs. 16772
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-sedf 5 xen-boot fail like 16772
test-amd64-amd64-xl-sedf-pin 10 guest-saverestore fail blocked in 16772
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass
version targeted for testing:
xen e31d4781c0e04bec01135dea0cb7d634ee035cd3
baseline version:
xen ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
George Dunlap <george.dunlap@eu.citrix.com>
Ian Campbell <ian.campbell@citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
Jan Beulich <jbeulich@suse.com>
Juergen Gross <juergen.gross@ts.fujitsu.com>
Keir Fraser <keir@xen.org>
Marcus Granado <marcus.granado@citrix.com>
Matthew Daley <mattjd@gmail.com>
Olaf Hering <olaf@aepfle.de>
Robbie VanVossen <robert.vanvossen@dornerworks.com>
Tim Deegan <tim@xen.org>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-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-win7-amd64 fail
test-amd64-i386-xl-qemut-win7-amd64 fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-win7-amd64 fail
test-amd64-i386-xl-win7-amd64 fail
test-amd64-i386-xl-credit2 fail
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-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-xl-sedf-pin fail
test-amd64-amd64-pv pass
test-amd64-i386-pv broken
test-amd64-amd64-xl-sedf fail
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
test-amd64-i386-xl-winxpsp3-vcpus1 fail
test-amd64-i386-xend-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-amd64-i386-xend-winxpsp3 fail
test-amd64-amd64-xl-winxpsp3 fail
------------------------------------------------------------
sg-report-flight on woking.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 411 lines long.)
Ian Jackson
2013-Mar-08 14:29 UTC
Re: [xen-unstable test] 17180: regressions - trouble: broken/fail/pass
xen.org writes ("[xen-unstable test] 17180: regressions - trouble:
broken/fail/pass"):> flight 17180 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/17180/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-xl-credit2 5 xen-boot fail REGR. vs. 16772
Mar 8 09:36:01.369651 (XEN) ****************************************
Mar 8 09:36:01.377561 (XEN) Panic on CPU 0:
Mar 8 09:36:01.377601 (XEN) Assertion ''rt_credit >= 0''
failed at sched_credit2.c:1559
Mar 8 09:36:01.377657 (XEN) ****************************************
Mar 8 09:36:01.385966 (XEN)
Mar 8 09:36:01.386001 (XEN) Reboot in five seconds...
No stack trace for some reason. I guess this is probably related to
c0704a8a or 8b3072a0.
Ian.
George Dunlap
2013-Mar-08 14:34 UTC
Re: [xen-unstable test] 17180: regressions - trouble: broken/fail/pass
On 08/03/13 14:29, Ian Jackson wrote:> xen.org writes ("[xen-unstable test] 17180: regressions - trouble: broken/fail/pass"): >> flight 17180 xen-unstable real [real] >> http://www.chiark.greenend.org.uk/~xensrcts/logs/17180/ >> >> Regressions :-( >> >> Tests which did not succeed and are blocking, >> including tests which could not be run: >> test-amd64-i386-xl-credit2 5 xen-boot fail REGR. vs. 16772 > Mar 8 09:36:01.369651 (XEN) **************************************** > Mar 8 09:36:01.377561 (XEN) Panic on CPU 0: > Mar 8 09:36:01.377601 (XEN) Assertion ''rt_credit >= 0'' failed at sched_credit2.c:1559 > Mar 8 09:36:01.377657 (XEN) **************************************** > Mar 8 09:36:01.385966 (XEN) > Mar 8 09:36:01.386001 (XEN) Reboot in five seconds... > > No stack trace for some reason. I guess this is probably related to > c0704a8a or 8b3072a0.Yes, Jan brought this to my attention yesterday; I''ve just posted a patch series fixing it, which Jan has some minor comments on. Would you like me to cc you on the resend? -George
Ian Jackson
2013-Mar-08 14:53 UTC
Re: [xen-unstable test] 17180: regressions - trouble: broken/fail/pass
George Dunlap writes ("Re: [xen-unstable test] 17180: regressions -
trouble: broken/fail/pass"):> On 08/03/13 14:29, Ian Jackson wrote:
> > No stack trace for some reason. I guess this is probably related to
> > c0704a8a or 8b3072a0.
>
> Yes, Jan brought this to my attention yesterday; I''ve just posted
a
> patch series fixing it, which Jan has some minor comments on. Would you
> like me to cc you on the resend?
Please, yes.
Ian.