|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable test] 4570: regressions - FAIL
flight 4570 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/4570/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-xcpkern-i386-xl-credit2 14 guest-localmigrate/x10 fail REGR. vs. 4535 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-win 16 leak-check/check fail never pass test-amd64-i386-rhel6hvm-amd 8 guest-saverestore fail never pass test-amd64-i386-rhel6hvm-intel 8 guest-saverestore fail never pass test-amd64-i386-win 16 leak-check/check fail never pass test-amd64-xcpkern-i386-rhel6hvm-amd 8 guest-saverestore fail never pass test-amd64-xcpkern-i386-rhel6hvm-intel 8 guest-saverestore fail never pass test-amd64-xcpkern-i386-win 16 leak-check/check fail never pass test-i386-i386-win 16 leak-check/check fail never pass test-i386-xcpkern-i386-win 16 leak-check/check fail never pass version targeted for testing: xen 7b4c82f07281 baseline version: xen 285a8f8d217e ------------------------------------------------------------ People who touched revisions under test: Allen Kay <allen.m.kay@xxxxxxxxx> Chun Yan Liu <cyliu@xxxxxxxxxx> Gianni Tedesco <gianni.tedesco@xxxxxxxxxx> Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxxxx> Jim Fehlig <jfehlig@xxxxxxxxxx> Keir Fraser <keir@xxxxxxx> Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> Wei Gang <gang.wei@xxxxxxxxx> ------------------------------------------------------------ jobs: build-i386-xcpkern pass 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 pass test-i386-i386-xl pass test-amd64-xcpkern-i386-xl pass test-i386-xcpkern-i386-xl pass test-amd64-i386-rhel6hvm-amd fail test-amd64-xcpkern-i386-rhel6hvm-amd fail test-amd64-i386-xl-credit2 pass 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 pass test-amd64-xcpkern-i386-xl-multivcpu pass 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 pass test-i386-xcpkern-i386-pv pass 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 ------------------------------------------------------------ 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: 22653:7b4c82f07281 tag: tip user: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> date: Wed Jan 05 23:54:15 2011 +0000 QEMU_TAG update changeset: 22652:77f1af42ca39 user: Yang Z Zhang <yang.z.zhang@xxxxxxxxx> date: Wed Jan 05 23:37:32 2011 +0000 libxl: fix free of uninitialised "disks" variable Reported-by: Wei Huang <wei.huang2@xxxxxxx> Reported-by: Christoph Egger <Christoph.Egger@xxxxxxx> Author: Yang Z Zhang <yang.z.zhang@xxxxxxxxx> Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> changeset: 22651:e0db3784a4a2 user: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> date: Wed Jan 05 23:31:24 2011 +0000 tools/xend: drbd: fix things by reverting 20158 drbd's block-drbd script handles all of the details that c/s 20158 introduces within xend :-(. This c/s should be reverted as it causes a regression. Jim Fehlig tested drbd without 20158 and it works fine. Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Tested-by: Jim Fehlig <jfehlig@xxxxxxxxxx> changeset: 22650:180ad8c642ab user: Gianni Tedesco <gianni.tedesco@xxxxxxxxxx> date: Wed Jan 05 23:13:07 2011 +0000 xl: don't segfault parsing disk configs, support NULL physpath and ioemu: Switch to a state machine parser since it's easier to handle all these exotic cases without segfaulting. NULL physpaths are now allowed and a dodgy hack is introduced to skip over the "ioemu:" prefix for a virtpath. Also fixes a leak of buf2. Signed-off-by: Gianni Tedesco <gianni.tedesco@xxxxxxxxxx> Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> changeset: 22649:39194f457534 user: Keir Fraser <keir@xxxxxxx> date: Wed Jan 05 09:57:15 2011 +0000 relax vCPU pinned checks Both writing of certain MSRs and VCPUOP_get_physid make sense also for dynamically (perhaps temporarily) pinned vcpus. Likely a couple of other MSR writes (MSR_K8_HWCR, MSR_AMD64_NB_CFG, MSR_FAM10H_MMIO_CONF_BASE) would make sense to be restricted by an is_pinned() check too, possibly also some MSR reads. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx> changeset: 22648:41a259d7a33d user: Keir Fraser <keir@xxxxxxx> date: Wed Jan 05 09:52:54 2011 +0000 x86 hvm: Add a missing line to record the type passed into register_io_handler() Add a missing line to record the type passed into register_io_handler() Without this line, the BUFFERED_IO handler was never called. Signed-off-by: Wei Gang <gang.wei@xxxxxxxxx> changeset: 22647:852d87e0480b user: Keir Fraser <keir@xxxxxxx> date: Wed Jan 05 09:52:18 2011 +0000 x86: Allow dom0 to write MSR IA32_ENERGY_PERF_BIAS Allow dom0 to write MSR IA32_ENERGY_PERF_BIAS There is a new hardware feature, which lets system software to set Energy Performance Preference. This is a opaque knob in the form of IA32_ENERGY_PERF_BIAS MSR, which has a 4 bit Energy Performance Preference Hint. The support for this feature is indicated by CPUID.06H.ECX.bit3. Refer to Intel Architectures Software Developer's Manual for more info. Let dom0 tools to control it. Signed-off-by: Wei Gang <gang.wei@xxxxxxxxx> changeset: 22646:e635e6641c07 user: Keir Fraser <keir@xxxxxxx> date: Wed Jan 05 09:50:21 2011 +0000 [VTD] added WLAN device ID on Fujitsu's platform in quirks.c Added WLAN device ID 0x422C that was found on Fujitsu's Calpella system to WLAN quirk. Signed-off-by: Allen Kay <allen.m.kay@xxxxxxxxx> changeset: 22645:76d897a06b31 user: Keir Fraser <keir@xxxxxxx> date: Wed Jan 05 09:48:43 2011 +0000 x86 amd: Revert 6382:b74c15e4dd4f (AMD flush filter configuration) Flush filter is not reliably supported by any processor, we already have code to unconditionally disable the filter, so we don't need the command-line config option. Remove it. Signed-off-by: Keir Fraser <keir@xxxxxxx> changeset: 22644:fece73d4d309 user: Tim Deegan <Tim.Deegan@xxxxxxxxxx> date: Wed Jan 05 09:41:28 2011 +0000 Enable 1GB HAP support by default. Signed-off-by: Allen Kay <allen.m.kay@xxxxxxxxx> changeset: 22643:285a8f8d217e user: Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> date: Tue Jan 04 15:40:00 2011 +0000 tools/gdbsx: Update gdbsx README Signed-off-by: Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> ======================================== commit 99d53fbb69d3e03be61ae10506a304a3d08d792f Author: Chun Yan Liu <cyliu@xxxxxxxxxx> Date: Wed Jan 5 23:48:36 2011 +0000 fix '|' key display problem in en-us with altgr processing Commit f95d202ed644 handles altgr-insert problem. Unfortunately, with that patch, there is a problem in En-us keyboard: '|' (bar) cannot be displayed. After checking keymap files, we found there are two definitions to "bar" in en-us: bar 0x56 altgr (in "common") bar 0x2b shift (in "en-us") First line is actually invalid in en-us lanuage. The 2nd definition will cover the 1st one. The previous change in didn't consider multi-definition case. It scans keymap files, if keysym needs altgr, it will records that, after that, if keysym is pressed but altgr not pressed, it will add an altgr press opeartion. It is correct if all keysyms are unique and valid. But in the above multi-definition case, there is problem: when reading bar 0x56 altgr (in "common") it will record altgr needed, but in fact, that definition won't be used, it always use the 2nd definition and won't need altgr. Then if the keysym is pressed, the code will still add an altgr press operation, that will cause problem. So, if we cannot avoid multi-definition in keymap files, the altgr flag (whether altgr needed or not) should also be refreshed according to the 2nd defintion. In the above case, when reading the 1st line, it records altgr needed; then reading 2nd line, 2nd definition will cover the 1st, meanwhile the altgr flag should be reset (the 2nd definition doesn't need altgr, so altgr flag should be removed.) Following patch supplements f95d202ed644, and solve the problem. Signed-off-by: Chun Yan Liu <cyliu@xxxxxxxxxx> Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |