On Sun, 2012-06-24 at 17:47 +0100, xen.org wrote:> flight 13361 linux-3.0 real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/13361/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-i386-i386-xl 5 xen-boot fail REGR. vs.
13100
This has failed a couple of time now.
[0] shows the test system waits from 2012-06-24 12:10:03 Z until
2012-06-24 12:16:46 Z for the machine to reappear on the network.
[1] shows that the system was fully booted at Jun 24 12:13:58.599838
which is in plenty of time. The brctl and route logs look sensible. The
ifconfig log shows an IP address in the right place and both TX and RX
packets being counted.
How synchronised are the clocks used in [0] and [1]?
Ian.
[0]
http://www.chiark.greenend.org.uk/~xensrcts/logs/13361/test-i386-i386-xl/5.ts-host-reboot.log
[1]
http://www.chiark.greenend.org.uk/~xensrcts/logs/13361/test-i386-i386-xl/serial-woodlouse.log
>
> Tests which are failing intermittently (not blocking):
> test-amd64-i386-xl-multivcpu 10 guest-saverestore fail pass in
13356
> test-amd64-i386-xl 5 xen-boot fail pass in
13356
>
> Regressions which are regarded as allowable (not blocking):
> test-amd64-amd64-xl-sedf 9 guest-start fail like
13100
> test-amd64-amd64-xl-qemuu-winxpsp3 12 guest-localmigrate/x10 fail like
13100
>
> Tests which did not succeed, but are not blocking:
> test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail never
pass
> test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never
pass
> test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never
pass
> test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never
pass
> test-i386-i386-xl-qemuu-winxpsp3 13 guest-stop fail never
pass
> test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never
pass
> test-amd64-i386-win 16 leak-check/check fail never
pass
> test-i386-i386-win 16 leak-check/check fail never
pass
> test-amd64-i386-win-vcpus1 16 leak-check/check fail never
pass
> test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never
pass
> test-amd64-i386-xl-win7-amd64 13 guest-stop 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-i386-i386-xl-winxpsp3 13 guest-stop fail never
pass
> test-amd64-amd64-xl-win 13 guest-stop fail never
pass
> test-amd64-amd64-win 16 leak-check/check fail never
pass
> test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail in 13356 never
pass
>
> version targeted for testing:
> linux c0bd4b6a0c6c0d42235920fb7ddd7110c86e2adb
> baseline version:
> linux 839cf7a236278ae358ff12141a168c0982fa0cd9
>
> jobs:
> build-amd64 pass
> build-i386 pass
> build-amd64-pvops pass
> build-i386-pvops pass
> test-amd64-amd64-xl pass
> test-amd64-i386-xl fail
> test-i386-i386-xl fail
> test-amd64-i386-rhel6hvm-amd pass
> test-amd64-i386-qemuu-rhel6hvm-amd pass
> 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-qemuu-rhel6hvm-intel pass
> test-amd64-i386-xl-multivcpu fail
> 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 pass
> test-i386-i386-pv pass
> test-amd64-amd64-xl-sedf fail
> 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
>
>
> Not pushing.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel