xen.org
2013-Oct-15 05:26 UTC
[xen-unstable test] 20890: trouble: blocked/broken/fail/pass
flight 20890 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/20890/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf 2 host-install(2) broken REGR. vs. 20855
build-armhf-pvops 2 host-install(2) broken REGR. vs. 20855
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-armhf-armhf-xl 1 xen-build-check(1) blocked n/a
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-xl-qemut-win7-amd64 13 guest-stop 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-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-xl-qemut-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-amd64-xl-qemut-win7-amd64 13 guest-stop fail never pass
version targeted for testing:
xen 6ef823fdfa701b3659e4161520f43b5835338fb5
baseline version:
xen 1a510f3c447452006fa2a661b387fdc5410c41d5
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Anthony PERARD <anthony.perard@citrix.com>
Daniel De Graaf <dgdegra@tycho.nsa.gov>
David Vrabel <david.vrabel@citrix.com>
Fabio Fantoni <fabio.fantoni@m2r.biz>
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>
Kristoffer Egefelt <kristoffer@itoc.dk>
Tril <tril@metapipe.net>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf broken
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-armhf-pvops broken
build-i386-pvops pass
test-amd64-amd64-xl pass
test-armhf-armhf-xl blocked
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 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-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-xl-sedf-pin pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-amd64-amd64-xl-sedf pass
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 437 lines long.)
Ian Campbell
2013-Oct-15 07:28 UTC
Re: [xen-unstable test] 20890: trouble: blocked/broken/fail/pass
On Tue, 2013-10-15 at 06:26 +0100, xen.org wrote:> flight 20890 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/20890/ > > Failures and problems with tests :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > build-armhf 2 host-install(2) broken REGR. vs. 20855 > build-armhf-pvops 2 host-install(2) broken REGR. vs. 20855From http://www.chiark.greenend.org.uk/~xensrcts/logs/20890/build-armhf/2.ts-host-install-twice.log 2013-10-14 22:38:02 Z power: setting 0 for marilith-n5 Traceback (most recent call last): File "/usr/groups/xencore/systems/bin/xenuse", line 388, in <module> main() File "/usr/groups/xencore/systems/bin/xenuse", line 356, in main machine.power(optPower, optForce) File "/usr/groups/xencore/systems/bin/xenuse", line 113, in power self.checkLocked(optForce, allowUnlocked = True) File "/usr/groups/xencore/systems/bin/xenuse", line 83, in checkLocked if l.strip() == ("LEASEUSER=''%s''" % os.environ["USER"]): File "/usr/lib/python2.5/UserDict.py", line 22, in __getitem__ raise KeyError(key) KeyError: ''USER'' /usr/groups/xencore/systems/bin/xenuse --off marilith-n5: 256 at Osstest.pm line 275. Looks like someone was messing with xenuse. Running it by hand this morning it seems to be OK now... Unless perhaps osstest is stripping $USER from the environment? If it is then grep doesn''t see where... I''m also now wondering how this ever worked, since the machines are xenuse locked by me and the tests are run as osstest, so xenuse ought to be rejecting attempts by osstest to do power control... Ian.
Ian Campbell
2013-Oct-15 08:25 UTC
Re: [xen-unstable test] 20890: trouble: blocked/broken/fail/pass
On Tue, 2013-10-15 at 08:28 +0100, Ian Campbell wrote:> I''m also now wondering how this ever worked, since the machines are > xenuse locked by me and the tests are run as osstest, so xenuse ought > to be rejecting attempts by osstest to do power control...I''ve now locked the machines while running as osstest and it seems to have done the right thing... Ian
Ian Campbell
2013-Oct-15 14:20 UTC
Re: [xen-unstable test] 20890: trouble: blocked/broken/fail/pass
On Tue, 2013-10-15 at 08:28 +0100, Ian Campbell wrote:> On Tue, 2013-10-15 at 06:26 +0100, xen.org wrote: > > flight 20890 xen-unstable real [real] > > http://www.chiark.greenend.org.uk/~xensrcts/logs/20890/ > > > > Failures and problems with tests :-( > > > > Tests which did not succeed and are blocking, > > including tests which could not be run: > > build-armhf 2 host-install(2) broken REGR. vs. 20855 > > build-armhf-pvops 2 host-install(2) broken REGR. vs. 20855 > > From > http://www.chiark.greenend.org.uk/~xensrcts/logs/20890/build-armhf/2.ts-host-install-twice.log > > 2013-10-14 22:38:02 Z power: setting 0 for marilith-n5 > Traceback (most recent call last): > File "/usr/groups/xencore/systems/bin/xenuse", line 388, in <module> > main() > File "/usr/groups/xencore/systems/bin/xenuse", line 356, in main > machine.power(optPower, optForce) > File "/usr/groups/xencore/systems/bin/xenuse", line 113, in power > self.checkLocked(optForce, allowUnlocked = True) > File "/usr/groups/xencore/systems/bin/xenuse", line 83, in checkLocked > if l.strip() == ("LEASEUSER=''%s''" % os.environ["USER"]): > File "/usr/lib/python2.5/UserDict.py", line 22, in __getitem__ > raise KeyError(key) > KeyError: ''USER'' > /usr/groups/xencore/systems/bin/xenuse --off marilith-n5: 256 at Osstest.pm line 275. > > Looks like someone was messing with xenuse. Running it by hand this > morning it seems to be OK now... > > Unless perhaps osstest is stripping $USER from the environment? If it is > then grep doesn''t see where...It turns out $USER is not required by any spec and cron (which runs osstest) does not set it. xenuse has been fixed to not rely on $USER.> > I''m also now wondering how this ever worked, since the machines are > xenuse locked by me and the tests are run as osstest, so xenuse ought to > be rejecting attempts by osstest to do power control... > > Ian. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel