xen.org
2012-Feb-05 19:58 UTC
[qemu-upstream-unstable test] 11890: tolerable FAIL - PUSHED
flight 11890 qemu-upstream-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/11890/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-pv 9 guest-start fail baseline untested
test-amd64-i386-xl 16 guest-start.2 fail baseline untested
Tests which did not succeed, but are not blocking:
test-i386-i386-xl-qemuu-winxpsp3 7 windows-install fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 7 windows-install fail never pass
test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-install fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail never pass
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-amd64-i386-rhel6hvm-amd 11 leak-check/check fail never pass
test-amd64-i386-qemuu-rhel6hvm-amd 7 redhat-install fail never pass
test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
test-i386-i386-xl-win 13 guest-stop fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-i386-i386-win 14 guest-start.2 fail never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass
version targeted for testing:
qemuu 86a8d63bc11431509506b95c1481e1a023302cbc
baseline version:
qemuu 85a4ca797dbe25f27df0a66aa4df1cab63245cd3
------------------------------------------------------------
People who touched revisions under test:
------------------------------------------------------------
jobs:
build-amd64 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 fail
test-i386-i386-xl pass
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-qemuu-rhel6hvm-amd 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 pass
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-qemuu-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-amd64-xl-sedf-pin pass
test-amd64-amd64-pv pass
test-amd64-i386-pv fail
test-i386-i386-pv pass
test-amd64-amd64-xl-sedf pass
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-i386-xl-winxpsp3-vcpus1 fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-i386-i386-xl-qemuu-winxpsp3 fail
test-amd64-i386-xend-winxpsp3 fail
test-amd64-amd64-xl-winxpsp3 fail
test-i386-i386-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
Pushing revision :
+ branch=qemu-upstream-unstable
+ revision=86a8d63bc11431509506b95c1481e1a023302cbc
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e ''
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
''
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ ''['' x ''!=''
x/export/home/osstest/repos/lock '']''
++ OSSTEST_REPOS_LOCK_LOCKED=/export/home/osstest/repos/lock
++ exec with-lock-ex -w /export/home/osstest/repos/lock ./ap-push
qemu-upstream-unstable 86a8d63bc11431509506b95c1481e1a023302cbc
+ branch=qemu-upstream-unstable
+ revision=86a8d63bc11431509506b95c1481e1a023302cbc
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e ''
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
''
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ ''['' x/export/home/osstest/repos/lock ''!=''
x/export/home/osstest/repos/lock '']''
+ . cri-common
++ umask 002
+ select_xenbranch
+ case "$branch" in
+ tree=qemuu
+ xenbranch=xen-unstable
+ : xen@xenbits.xensource.com
+ : xen@xenbits.xensource.com:git/linux-pvops
+ : master
+ : tested/2.6.39.x
+ : xen@xenbits.xensource.com:git/qemu-upstream-unstable.git
+ . ap-common
++ : http://xenbits.xen.org/staging/xen-unstable.hg
++ : git://xenbits.xen.org/staging/qemu-xen-unstable.git
++ : git://git.kernel.org
++ : xen@xenbits.xensource.com:git/linux-pvops
++ : master
++ : git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
++ : tested/2.6.39.x
++ : daily-cron.qemu-upstream-unstable
++ : http://hg.uk.xensource.com/carbon/trunk/linux-2.6.27
++ : xen@xenbits.xensource.com:git/qemu-upstream-unstable.git
++ : daily-cron.qemu-upstream-unstable
+ case "$branch" in
+ cd /export/home/osstest/repos/qemu-upstream-unstable
+ git push xen@xenbits.xensource.com:git/qemu-upstream-unstable.git
86a8d63bc11431509506b95c1481e1a023302cbc:master
Counting objects: 52
Counting objects: 64, done.
Compressing objects: 7% (1/14)
Compressing objects: 14% (2/14)
Compressing objects: 21% (3/14)
Compressing objects: 28% (4/14)
Compressing objects: 35% (5/14)
Compressing objects: 42% (6/14)
Compressing objects: 50% (7/14)
Compressing objects: 57% (8/14)
Compressing objects: 64% (9/14)
Compressing objects: 71% (10/14)
Compressing objects: 78% (11/14)
Compressing objects: 85% (12/14)
Compressing objects: 92% (13/14)
Compressing objects: 100% (14/14)
Compressing objects: 100% (14/14), done.
Writing objects: 2% (1/49)
Writing objects: 4% (2/49)
Writing objects: 6% (3/49)
Writing objects: 8% (4/49)
Writing objects: 10% (5/49)
Writing objects: 12% (6/49)
Writing objects: 14% (7/49)
Writing objects: 16% (8/49)
Writing objects: 18% (9/49)
Writing objects: 20% (10/49)
Writing objects: 22% (11/49)
Writing objects: 24% (12/49)
Writing objects: 26% (13/49)
Writing objects: 28% (14/49)
Writing objects: 30% (15/49)
Writing objects: 32% (16/49)
Writing objects: 34% (17/49)
Writing objects: 36% (18/49)
Writing objects: 38% (19/49)
Writing objects: 40% (20/49)
Writing objects: 42% (21/49)
Writing objects: 46% (23/49)
Writing objects: 48% (24/49)
Writing objects: 51% (25/49)
Writing objects: 53% (26/49)
Writing objects: 55% (27/49)
Writing objects: 57% (28/49)
Writing objects: 59% (29/49)
Writing objects: 61% (30/49)
Writing objects: 63% (31/49)
Writing objects: 65% (32/49)
Writing objects: 67% (33/49)
Writing objects: 69% (34/49)
Writing objects: 71% (35/49)
Writing objects: 73% (36/49)
Writing objects: 75% (37/49)
Writing objects: 77% (38/49)
Writing objects: 79% (39/49)
Writing objects: 81% (40/49)
Writing objects: 83% (41/49)
Writing objects: 85% (42/49)
Writing objects: 87% (43/49)
Writing objects: 89% (44/49)
Writing objects: 91% (45/49)
Writing objects: 93% (46/49)
Writing objects: 95% (47/49)
Writing objects: 97% (48/49)
Writing objects: 100% (49/49)
Writing objects: 100% (49/49), 9.77 KiB, done.
Total 49 (delta 37), reused 47 (delta 35)
To xen@xenbits.xensource.com:git/qemu-upstream-unstable.git
85a4ca7..86a8d63 86a8d63bc11431509506b95c1481e1a023302cbc -> master
Ian Jackson
2012-Feb-07 17:58 UTC
Re: [qemu-upstream-unstable test] 11890: tolerable FAIL - PUSHED
xen.org writes ("[Xen-devel] [qemu-upstream-unstable test] 11890: tolerable
FAIL - PUSHED"):> test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-install fail never
pass
I added some tests where the qemu version is set to "qemu-xen". They
currently all fail with this error message:
xl: libxl_dm.c:366: libxl__build_device_model_args_new: Assertion
`!"missing code for supplying vnc password to qemu"'' failed.
I think this is a pretty important feature so I don''t think I should
work around it in my test system.
Adding this so that the tests work is not critical for the general
development of Xen, as pushes will carry on regardless, but to get the
best value out of the push gate (eg, to stop pushes of xen-unstable
which break when used with qemu upstream) it would be nice to fix
this.
Ian.