flight 18104 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/18104/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail pass in 18103
test-amd64-amd64-xl-sedf-pin 11 guest-localmigrate fail pass in 18103
test-amd64-amd64-xl-qemuu-winxpsp3 10 guest-saverestore.2 fail pass in 18103
test-amd64-i386-xl-multivcpu 4 xen-install fail pass in 18103
test-amd64-amd64-xl-win7-amd64 4 xen-install fail pass in 18103
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-pcipt-intel 9 guest-start 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-win7-amd64 13 guest-stop 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-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-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail in 18103 never pass
test-amd64-amd64-xl-win7-amd64 13 guest-stop fail in 18103 never pass
version targeted for testing:
xen 6859874b61d5ddaf5289e72ed2b2157739b72ca5
baseline version:
xen 6859874b61d5ddaf5289e72ed2b2157739b72ca5
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 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 fail
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-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
Published tested tree is already up to date.
>>> On 12.06.13 at 09:14, xen.org <ian.jackson@eu.citrix.com> wrote: > flight 18104 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/18104/ > > Failures :-/ but no regressions. > > Tests which are failing intermittently (not blocking): > test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail pass in 18103 > test-amd64-amd64-xl-sedf-pin 11 guest-localmigrate fail pass in 18103 > test-amd64-amd64-xl-qemuu-winxpsp3 10 guest-saverestore.2 fail pass in 18103 > test-amd64-i386-xl-multivcpu 4 xen-install fail pass in 18103 > test-amd64-amd64-xl-win7-amd64 4 xen-install fail pass in 18103Quite a bunch of spurious(?) failures at once, several of them on earwig - was there any change to the host software set or the test infrastructure? In any case, I wasn''t able to spot for any of them why they actually failed... Jan
Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 18104: tolerable
FAIL"):> Quite a bunch of spurious(?) failures at once, several of them on
> earwig - was there any change to the host software set or the
> test infrastructure? In any case, I wasn''t able to spot for any of
> them why they actually failed...
No, nothing has changed AFAIAA. It''s possible that something in the
CMOS settings has been corrupted - earwig has a history of unexplained
changes to CMOS settings. I could have a look and see what there is
to see.
Failures like this one
> test-amd64-i386-xl-multivcpu 4 xen-install fail pass in 18103
Found linux image: /boot/vmlinuz-2.6.32.57
2013-06-12 03:27:40 Z command timed out [30]: ssh -o
StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o
ServerAliveInterval=100 -o PasswordAuthentication=no -o
ChallengeResponseAuthentication=no -o
UserKnownHostsFile=tmp/t.known_hosts_18104.test-amd64-i386-xl-multivcpu
root@10.80.248.97 update-grub
suggest something other than bugs in the software under test. Maybe
the hardware has become flaky somehow.
Ian.