|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.0-testing test] 8010: tolerable FAIL
flight 8010 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8010/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: build-i386-oldkern 4 xen-build fail like 7681 test-amd64-i386-xl-multivcpu 15 guest-stop fail never pass test-amd64-amd64-xl 15 guest-stop fail never pass test-amd64-xcpkern-i386-xl-credit2 15 guest-stop fail never pass test-amd64-xcpkern-i386-xl-multivcpu 15 guest-stop fail never pass test-i386-xcpkern-i386-xl 15 guest-stop fail never pass test-amd64-xcpkern-i386-pv 18 leak-check/check fail like 7681 test-amd64-i386-xl-credit2 5 xen-boot fail like 7681 test-amd64-xcpkern-i386-xl 15 guest-stop fail never pass test-i386-i386-xl 15 guest-stop fail never pass test-amd64-i386-xl 15 guest-stop fail never pass test-amd64-amd64-win 16 leak-check/check fail never pass test-i386-i386-win 16 leak-check/check fail never pass test-amd64-i386-rhel6hvm-intel 7 redhat-install fail never pass test-amd64-xcpkern-i386-rhel6hvm-amd 7 redhat-install fail never pass test-amd64-xcpkern-i386-rhel6hvm-intel 7 redhat-install fail never pass test-amd64-i386-rhel6hvm-amd 7 redhat-install fail never pass test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass test-amd64-xcpkern-i386-win 16 leak-check/check fail never pass test-i386-xcpkern-i386-win 16 leak-check/check fail never pass test-amd64-i386-win 16 leak-check/check fail never pass test-amd64-xcpkern-i386-xl-win 7 windows-install fail never pass test-amd64-i386-xl-win-vcpus1 7 windows-install fail never pass test-amd64-amd64-xl-win 7 windows-install fail never pass test-i386-i386-xl-win 7 windows-install fail never pass version targeted for testing: xen a353b8304f7a baseline version: xen 600e224e8c51 ------------------------------------------------------------ People who touched revisions under test: Keir Fraser <keir@xxxxxxx> Liu, Jinsong <jinsong.liu@xxxxxxxxx> Paul Durrant <paul.durrant@xxxxxxxxxx> Tim Deegan <Tim.Deegan@xxxxxxxxxx> ------------------------------------------------------------ jobs: build-i386-xcpkern pass build-amd64 pass build-i386 pass build-amd64-oldkern pass build-i386-oldkern fail build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl fail test-amd64-i386-xl fail test-i386-i386-xl fail test-amd64-xcpkern-i386-xl fail test-i386-xcpkern-i386-xl fail test-amd64-i386-rhel6hvm-amd fail test-amd64-xcpkern-i386-rhel6hvm-amd fail test-amd64-i386-xl-credit2 fail test-amd64-xcpkern-i386-xl-credit2 fail test-amd64-i386-rhel6hvm-intel fail test-amd64-xcpkern-i386-rhel6hvm-intel fail test-amd64-i386-xl-multivcpu fail test-amd64-xcpkern-i386-xl-multivcpu fail test-amd64-amd64-pair pass test-amd64-i386-pair pass test-i386-i386-pair pass test-amd64-xcpkern-i386-pair pass test-i386-xcpkern-i386-pair pass test-amd64-amd64-pv pass test-amd64-i386-pv pass test-i386-i386-pv pass test-amd64-xcpkern-i386-pv fail test-i386-xcpkern-i386-pv pass test-amd64-i386-win-vcpus1 fail test-amd64-i386-xl-win-vcpus1 fail test-amd64-amd64-win fail test-amd64-i386-win fail test-i386-i386-win fail test-amd64-xcpkern-i386-win fail test-i386-xcpkern-i386-win fail test-amd64-amd64-xl-win fail test-i386-i386-xl-win fail test-amd64-xcpkern-i386-xl-win 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. ------------------------------------------------------------ changeset: 21519:a353b8304f7a tag: tip user: Paul Durrant <paul.durrant@xxxxxxxxxx> date: Fri Jul 08 09:02:03 2011 +0100 x86/hvm: Don't expose CPUID time leaf when not using PVRDTSCP Some versions of Oracle's Solaris PV drivers make a check that the maximal Xen hypervisor CPUID leaf is <= base leaf + 2 and refuse to work if this is not the case. The addition of the time leaf makes the maximal leaf == base leaf + 3 so this patch introduces a workaround that obscures the time leaf unless PVRDTSCP is in operation. Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx> xen-unstable changeset: 23661:8fe6f4be18aa xen-unstable date: Fri Jul 08 08:31:10 2011 +0100 changeset: 21518:a9c73a1e746a user: Liu, Jinsong <jinsong.liu@xxxxxxxxx> date: Fri Jul 08 09:01:08 2011 +0100 x86 cpu: Fix bug: unify cpu_dev attr as __cpuinitdata Currently different x86 cpu define different attr for cpu_dev. Some cpu define as __initdata, this would be risk under cpu hotplug. This patch fix the bug, unify them as __cpuinitdata, as what AMD cpu define now. Signed-off-by: Liu, Jinsong <jinsong.liu@xxxxxxxxx> Shan, Haitao <haitao.shan@xxxxxxxxx> xen-unstable changeset: 23659:7fe0331986c5 xen-unstable date: Fri Jul 08 08:30:41 2011 +0100 changeset: 21517:9199d2b31625 user: Tim Deegan <Tim.Deegan@xxxxxxxxxx> date: Fri Jul 08 09:00:22 2011 +0100 x86: fix boot-time watchdog test. Since the perf counter that the LAPIC NMI watchdog uses only runs while the core isn't halted, and all APs are idle at this point in the boot process, it's possible that remote CPUs won't see any NMIs during the 10-tick waiting period. Force all CPUs to busy-wait so we know the timers are running. Signed-off-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx> xen-unstable changeset: 23612:6c7a23e08a04 xen-unstable date: Tue Jun 28 09:16:13 2011 +0100 changeset: 21516:600e224e8c51 user: Keir Fraser <keir@xxxxxxx> date: Thu Jun 23 12:06:36 2011 +0100 xen-detect: Fix cpuid asm for 32-bit PIC compilation. Signed-off-by: Keir Fraser <keir@xxxxxxx> xen-unstable changeset: 23553:eca057e4475c xen-unstable date: Fri Jun 17 08:08:13 2011 +0100 (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |