|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-4.5-testing test] 63268: regressions - trouble: blocked/broken/fail/pass
flight 63268 xen-4.5-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/63268/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 5 xen-build fail REGR. vs. 63099 build-armhf 4 host-build-prep fail in 63214 REGR. vs. 63099 Tests which are failing intermittently (not blocking): test-amd64-i386-xl 3 host-install(3) broken pass in 63214 test-amd64-i386-qemut-rhel6hvm-amd 3 host-install(3) broken pass in 63214 test-amd64-i386-libvirt-pair 4 host-install/dst_host(4) broken pass in 63214 test-amd64-amd64-libvirt-vhd 3 host-install(3) broken pass in 63214 test-amd64-i386-xl-qemuu-win7-amd64 3 host-install(3) broken pass in 63214 test-amd64-i386-libvirt 14 guest-saverestore fail in 63214 pass in 63268 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail in 63214 pass in 63268 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 16 guest-localmigrate/x10 fail pass in 63214 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-rtds 6 xen-boot fail REGR. vs. 63099 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail in 63214 blocked in 63099 test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail in 63214 like 63099 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 63099 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 63099 Tests which did not succeed, but are not blocking: test-armhf-armhf-xl-vhd 1 build-check(1) blocked n/a test-armhf-armhf-libvirt-qcow2 1 build-check(1) blocked n/a test-armhf-armhf-libvirt-raw 1 build-check(1) blocked n/a test-armhf-armhf-xl-rtds 1 build-check(1) blocked n/a test-armhf-armhf-xl-arndale 1 build-check(1) blocked n/a test-armhf-armhf-libvirt 1 build-check(1) blocked n/a test-armhf-armhf-xl-credit2 1 build-check(1) blocked n/a test-armhf-armhf-xl-multivcpu 1 build-check(1) blocked n/a test-armhf-armhf-xl-cubietruck 1 build-check(1) blocked n/a build-armhf-libvirt 1 build-check(1) blocked n/a test-armhf-armhf-xl 1 build-check(1) blocked n/a test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail in 63214 never pass test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail never pass version targeted for testing: xen a5d0480d9c5b36b5f47459ce92ed3c67b7bed51d baseline version: xen 80e9f5624f9d1ef2e7bbd9b9b185e96b45e1bb17 Last test of basis 63099 2015-10-20 17:40:41 Z 4 days Failing since 63155 2015-10-21 15:43:44 Z 3 days 3 attempts Testing same since 63214 2015-10-22 13:24:43 Z 2 days 2 attempts ------------------------------------------------------------ People who touched revisions under test: Ian Campbell <ian.campbell@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Julien Grall <julien.grall@xxxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> Yang Zhang <yang.z.zhang@xxxxxxxxx> jobs: build-amd64 pass build-armhf fail build-i386 pass build-amd64-libvirt pass build-armhf-libvirt blocked build-i386-libvirt pass build-amd64-prev pass build-i386-prev pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass build-amd64-rumpuserxen pass build-i386-rumpuserxen pass test-amd64-amd64-xl pass test-armhf-armhf-xl blocked test-amd64-i386-xl broken test-amd64-amd64-xl-pvh-amd fail test-amd64-i386-qemut-rhel6hvm-amd broken test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemut-debianhvm-amd64 pass test-amd64-i386-xl-qemut-debianhvm-amd64 pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 pass test-amd64-amd64-rumpuserxen-amd64 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-i386-xl-qemuu-win7-amd64 broken test-armhf-armhf-xl-arndale blocked test-amd64-amd64-xl-credit2 pass test-armhf-armhf-xl-credit2 blocked test-armhf-armhf-xl-cubietruck blocked test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumpuserxen-i386 pass test-amd64-amd64-xl-pvh-intel fail test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt blocked test-amd64-i386-libvirt pass test-amd64-amd64-migrupgrade pass test-amd64-i386-migrupgrade pass test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu blocked test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair broken test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub pass test-amd64-amd64-pygrub pass test-armhf-armhf-libvirt-qcow2 blocked test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw blocked test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds fail test-armhf-armhf-xl-rtds blocked test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-amd64-libvirt-vhd broken test-armhf-armhf-xl-vhd blocked test-amd64-amd64-xl-qemut-winxpsp3 pass test-amd64-i386-xl-qemut-winxpsp3 pass test-amd64-amd64-xl-qemuu-winxpsp3 pass test-amd64-i386-xl-qemuu-winxpsp3 pass ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary broken-step test-amd64-i386-xl host-install(3) broken-step test-amd64-i386-qemut-rhel6hvm-amd host-install(3) broken-step test-amd64-i386-libvirt-pair host-install/dst_host(4) broken-step test-amd64-amd64-libvirt-vhd host-install(3) broken-step test-amd64-i386-xl-qemuu-win7-amd64 host-install(3) Not pushing. ------------------------------------------------------------ commit a5d0480d9c5b36b5f47459ce92ed3c67b7bed51d Author: Julien Grall <julien.grall@xxxxxxxxxx> Date: Thu Sep 17 18:36:36 2015 +0100 tools/libxc: arm: Check the index before accessing the bank When creating a guest with more than 3GB of memory, the 2 banks will be used and the loop with overrunning. The code will fail later on because Xen will deny to populate the region: domainbuilder: detail: xc_dom_devicetree_mem: called domainbuilder: detail: xc_dom_mem_init: mem 3096 MB, pages 0xc1800 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0xc1800 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: set_mode: guest xen-3.0-aarch64, address size 64 domainbuilder: detail: xc_dom_malloc : 14384 kB domainbuilder: detail: populate_guest_memory: populating RAM @0000000040000000-0000000100000000 (3072MB) domainbuilder: detail: populate_one_size: populated 0x3/0x3 entries with shift 18 domainbuilder: detail: populate_guest_memory: populating RAM @0000000200000000-0000000201800000 (24MB) domainbuilder: detail: populate_one_size: populated 0xc/0xc entries with shift 9 domainbuilder: detail: populate_guest_memory: populating RAM @0000007fad41c000-0007fb39dd42c000 (2141954816MB) domainbuilder: detail: populate_one_size: populated 0x100/0x1e4 entries with shift 0 domainbuilder: detail: populate_guest_memory: Not enough RAM This is because we are currently accessing the bank before checking the validity of the index. AFAICT, on Debian Jessie, the compiler (gcc 4.9.2) is assuming that it's not necessary to verify the index because it's used before. This is a valid assumption because the operand of && are execute from from left to right. Re-order the checks to verify the validity of the index before accessing the bank. The problem has been present since the introduction of the multi-bank feature in commit 45d9867837f099e9eed4189dac5ed39d1fe2ed49 " tools: arm: prepare domain builder for multiple banks of guest RAM". Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> (cherry picked from commit ed5c2c05cfa557b2391aef9557864d8d958d8d84) commit 9befcd335c21818caaf5c5ab764d31a4006d2800 Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Thu Aug 6 11:55:57 2015 +0100 libxl: use correct command line for arm guests. We need to use libxl__domain_build_state.pv_cmdline in order to pickup the correct args when using pygrub. libxl_domain_build_info.cmdline is any args statically configured by the user. This is consistent with the call to xc_domain_allocate, which takes the cmdline too (in that case for x86/PV usage). state->pv_cmdline is also set for non-pygrub guests, since libxl__bootloader_run propagates info->cmdline if no bootloader is configured. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> (cherry picked from commit 201eac83831d94ba2e9a63a7eed4c128633fafb1) commit 53c11b041793944e26165f294fb96242c459d197 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Oct 21 17:33:32 2015 +0200 x86/NUMA: fix SRAT table processor entry parsing and consumption - don't overrun apicid_to_node[] (possible in the x2APIC case) - don't limit number of processor related SRAT entries we can consume - make acpi_numa_{processor,x2apic}_affinity_init() as similar to one another as possible - print APIC IDs in hex (to ease matching with other log messages), at once making legacy and x2APIC ones distinguishable (by width) Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 83281fc9b31396e94c0bfb6550b75c165037a0ad master date: 2015-10-14 12:46:27 +0200 commit 0368463ece89a400c2f63800b782929d4b5fb949 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Oct 21 17:31:02 2015 +0200 x86: hide MWAITX from PV domains Since MWAIT is hidden too. (Linux starting with 4.3 is making use of that feature, and is checking for it without looking at the MWAIT one.) Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 941cd44324db7eddc46cba4596fa13d505066ccf master date: 2015-10-13 17:17:52 +0200 commit a262a89198551d5b74477b21cdc733ce414c1ff0 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Oct 21 17:30:12 2015 +0200 VT-d: don't suppress invalidation address write when it is zero GFN zero is a valid address, and hence may need invalidation done for it just like for any other GFN. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Yang Zhang <yang.z.zhang@xxxxxxxxx> master commit: 710942e57fb42ff8f344ca82f6b678f67e38ae63 master date: 2015-10-12 15:58:35 +0200 (qemu changes not included) _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |