flight 17139 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/17139/
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
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 7 debian-install fail blocked in 16772
test-amd64-amd64-xl-qemut-win 7 windows-install fail like 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-qemut-win-vcpus1 16 leak-check/check fail never pass
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-i386-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-win-vcpus1 13 guest-stop fail never pass
test-amd64-amd64-qemut-win 16 leak-check/check 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-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-xl-qemut-win-vcpus1 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-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop 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-qemuu-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-qemut-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
version targeted for testing:
xen 9581c4f9a55372a21e759cd449cb676d0e8feddb
baseline version:
xen ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc
------------------------------------------------------------
People who touched revisions under test:
Keir Fraser <keir@xen.org>
Matthew Daley <mattjd@gmail.com>
------------------------------------------------------------
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 pass
test-amd64-amd64-xl-sedf fail
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-qemut-win-vcpus1 fail
test-amd64-i386-xl-qemut-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
test-amd64-i386-xl-winxpsp3-vcpus1 fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-amd64-amd64-qemut-win fail
test-amd64-i386-qemut-win fail
test-amd64-amd64-xl-qemut-win fail
test-amd64-amd64-xl-win 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.
------------------------------------------------------------
commit 9581c4f9a55372a21e759cd449cb676d0e8feddb
Author: Matthew Daley <mattjd@gmail.com>
Date: Wed Mar 6 17:10:26 2013 +0100
fix domain unlocking in some xsm error paths
A couple of xsm error/access-denied code paths in hypercalls neglect to
unlock a previously locked domain. Fix by ensuring the domains are
unlocked correctly.
Signed-off-by: Matthew Daley <mattjd@gmail.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
(qemu changes not included)
>>> On 07.03.13 at 13:38, xen.org <ian.jackson@eu.citrix.com> wrote: > flight 17139 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/17139/ > > 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. 16772George, pretty likely something you want to take a look at: Mar 7 02:39:54.552252 (XEN) **************************************** Mar 7 02:39:54.560215 (XEN) Panic on CPU 0: Mar 7 02:39:54.560256 (XEN) Assertion ''rt_credit >= 0'' failed at sched_credit2.c:1559 Mar 7 02:39:54.560314 (XEN) **************************************** Jan
On 07/03/13 12:48, Jan Beulich wrote:>>>> On 07.03.13 at 13:38, xen.org <ian.jackson@eu.citrix.com> wrote: >> flight 17139 xen-unstable real [real] >> http://www.chiark.greenend.org.uk/~xensrcts/logs/17139/ >> >> 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 > George, > > pretty likely something you want to take a look at: > > Mar 7 02:39:54.552252 (XEN) **************************************** > Mar 7 02:39:54.560215 (XEN) Panic on CPU 0: > Mar 7 02:39:54.560256 (XEN) Assertion ''rt_credit >= 0'' failed at sched_credit2.c:1559 > Mar 7 02:39:54.560314 (XEN) ****************************************Very interesting... it seems that under certain circumstances, even if the scheduler sets a timer to pre-empt a VM for 200us, that the VM may run for >11ms. Since the "reset" assumes that your negative credit will never be less than -200us, it merely adds 10ms. So even after the reset, the VM is still in negative credits. Let me see what I want to do about that... -George