|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [qemu-mainline test] 50696: trouble: blocked/broken/pass
flight 50696 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/50696/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-xsm 3 host-install(3) broken REGR. vs. 50391 build-armhf 3 host-install(3) broken REGR. vs. 50391 build-i386-pvops 3 host-install(3) broken REGR. vs. 50391 build-amd64-xsm 3 host-install(3) broken REGR. vs. 50391 build-amd64-pvops 3 host-install(3) broken REGR. vs. 50391 build-amd64 3 host-install(3) broken REGR. vs. 50391 build-i386 3 host-install(3) broken REGR. vs. 50391 build-armhf-pvops 3 host-install(3) broken REGR. vs. 50391 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a test-amd64-amd64-xl-pvh-amd 1 build-check(1) blocked n/a test-amd64-amd64-libvirt-xsm 1 build-check(1) blocked n/a test-amd64-amd64-xl-xsm 1 build-check(1) blocked n/a test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a test-amd64-i386-xl-xsm 1 build-check(1) blocked n/a test-amd64-i386-libvirt-xsm 1 build-check(1) blocked n/a test-amd64-i386-freebsd10-i386 1 build-check(1) blocked n/a test-armhf-armhf-xl-xsm 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm 1 build-check(1) blocked n/a test-amd64-amd64-xl-pvh-intel 1 build-check(1) blocked n/a test-amd64-i386-xl-qemut-debianhvm-amd64-xsm 1 build-check(1) blocked n/a build-amd64-libvirt 1 build-check(1) blocked n/a test-amd64-i386-freebsd10-amd64 1 build-check(1) blocked n/a test-amd64-amd64-xl 1 build-check(1) blocked n/a test-amd64-amd64-xl-multivcpu 1 build-check(1) blocked n/a test-armhf-armhf-xl-arndale 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-xl-sedf-pin 1 build-check(1) blocked n/a test-amd64-i386-xl-qemut-winxpsp3-vcpus1 1 build-check(1) blocked n/a test-amd64-amd64-xl-credit2 1 build-check(1) blocked n/a test-amd64-i386-xl-qemut-winxpsp3 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-debianhvm-amd64 1 build-check(1) blocked n/a test-amd64-i386-qemut-rhel6hvm-intel 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemut-winxpsp3 1 build-check(1) blocked n/a test-amd64-i386-xl-qemut-win7-amd64 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemut-debianhvm-amd64 1 build-check(1) blocked n/a test-amd64-i386-qemut-rhel6hvm-amd 1 build-check(1) blocked n/a test-amd64-amd64-pair 1 build-check(1) blocked n/a test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 1 build-check(1) blocked n/a test-armhf-armhf-xl 1 build-check(1) blocked n/a test-armhf-armhf-xl-credit2 1 build-check(1) blocked n/a test-amd64-i386-libvirt 1 build-check(1) blocked n/a test-amd64-i386-xl 1 build-check(1) blocked n/a test-amd64-i386-qemuu-rhel6hvm-amd 1 build-check(1) blocked n/a test-armhf-armhf-xl-sedf 1 build-check(1) blocked n/a test-armhf-armhf-xl-sedf-pin 1 build-check(1) blocked n/a test-amd64-i386-qemuu-rhel6hvm-intel 1 build-check(1) blocked n/a test-armhf-armhf-xl-multivcpu 1 build-check(1) blocked n/a test-amd64-i386-rhel6hvm-intel 1 build-check(1) blocked n/a build-i386-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-xl-win7-amd64 1 build-check(1) blocked n/a test-amd64-amd64-xl-sedf 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemut-win7-amd64 1 build-check(1) blocked n/a test-amd64-i386-xl-qemuu-winxpsp3 1 build-check(1) blocked n/a test-armhf-armhf-libvirt 1 build-check(1) blocked n/a test-amd64-i386-rhel6hvm-amd 1 build-check(1) blocked n/a test-armhf-armhf-xl-cubietruck 1 build-check(1) blocked n/a test-armhf-armhf-libvirt-xsm 1 build-check(1) blocked n/a test-amd64-i386-xl-qemut-debianhvm-amd64 1 build-check(1) blocked n/a test-amd64-i386-xl-qemuu-debianhvm-amd64 1 build-check(1) blocked n/a test-amd64-i386-pair 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a build-armhf-libvirt 1 build-check(1) blocked n/a test-amd64-i386-xl-winxpsp3-vcpus1 1 build-check(1) blocked n/a test-amd64-i386-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a test-amd64-amd64-xl-winxpsp3 1 build-check(1) blocked n/a test-amd64-i386-xl-winxpsp3 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-winxpsp3 1 build-check(1) blocked n/a test-amd64-i386-xl-qemuu-win7-amd64 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-win7-amd64 1 build-check(1) blocked n/a test-amd64-i386-xl-win7-amd64 1 build-check(1) blocked n/a version targeted for testing: qemuu 638b8366200130cc7cf7a026630bc6bfb63b0c4c baseline version: qemuu 58c24a4775ef7ccf16cfcd695753dfdf149fe29d ------------------------------------------------------------ People who touched revisions under test: Alberto Garcia <berto@xxxxxxxxxx> Andreas Färber <afaerber@xxxxxxx> Dirk Mueller <dmueller@xxxxxxxx> Dirk Müller <dirk@xxxxxxxx> Edgar E. Iglesias <edgar.iglesias@xxxxxxxxxx> Gabriel L. Somlo <somlo@xxxxxxx> Gabriel Somlo <somlo@xxxxxxx> Gerd Hoffmann <kraxel@xxxxxxxxxx> Jordan Justen <jordan.l.justen@xxxxxxxxx> Leon Alrae <leon.alrae@xxxxxxxxxx> Mark Cave-Ayland <mark.cave-ayland@xxxxxxxxxxxx> Paolo Bonzini <pbonzini@xxxxxxxxxx> Peter Maydell <peter.maydell@xxxxxxxxxx> Thomas Huth <thuth@xxxxxxxxxx> ------------------------------------------------------------ jobs: build-amd64-xsm broken build-armhf-xsm broken build-i386-xsm pass build-amd64 broken build-armhf broken build-i386 broken build-amd64-libvirt blocked build-armhf-libvirt blocked build-i386-libvirt blocked build-amd64-pvops broken build-armhf-pvops broken build-i386-pvops broken test-amd64-amd64-xl blocked test-armhf-armhf-xl blocked test-amd64-i386-xl blocked test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm blocked test-amd64-i386-xl-qemut-debianhvm-amd64-xsm blocked test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm blocked test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm blocked test-amd64-amd64-libvirt-xsm blocked test-armhf-armhf-libvirt-xsm blocked test-amd64-i386-libvirt-xsm blocked test-amd64-amd64-xl-xsm blocked test-armhf-armhf-xl-xsm blocked test-amd64-i386-xl-xsm blocked test-amd64-amd64-xl-pvh-amd blocked test-amd64-i386-rhel6hvm-amd blocked test-amd64-i386-qemut-rhel6hvm-amd blocked test-amd64-i386-qemuu-rhel6hvm-amd blocked test-amd64-amd64-xl-qemut-debianhvm-amd64 blocked test-amd64-i386-xl-qemut-debianhvm-amd64 blocked test-amd64-amd64-xl-qemuu-debianhvm-amd64 blocked test-amd64-i386-xl-qemuu-debianhvm-amd64 blocked test-amd64-i386-freebsd10-amd64 blocked test-amd64-amd64-xl-qemuu-ovmf-amd64 blocked test-amd64-i386-xl-qemuu-ovmf-amd64 blocked test-amd64-amd64-xl-qemut-win7-amd64 blocked test-amd64-i386-xl-qemut-win7-amd64 blocked test-amd64-amd64-xl-qemuu-win7-amd64 blocked test-amd64-i386-xl-qemuu-win7-amd64 blocked test-amd64-amd64-xl-win7-amd64 blocked test-amd64-i386-xl-win7-amd64 blocked test-armhf-armhf-xl-arndale blocked test-amd64-amd64-xl-credit2 blocked test-armhf-armhf-xl-credit2 blocked test-armhf-armhf-xl-cubietruck blocked test-amd64-i386-freebsd10-i386 blocked test-amd64-amd64-xl-pvh-intel blocked test-amd64-i386-rhel6hvm-intel blocked test-amd64-i386-qemut-rhel6hvm-intel blocked test-amd64-i386-qemuu-rhel6hvm-intel blocked test-amd64-amd64-libvirt blocked test-armhf-armhf-libvirt blocked test-amd64-i386-libvirt blocked test-amd64-amd64-xl-multivcpu blocked test-armhf-armhf-xl-multivcpu blocked test-amd64-amd64-pair blocked test-amd64-i386-pair blocked test-amd64-amd64-xl-sedf-pin blocked test-armhf-armhf-xl-sedf-pin blocked test-amd64-amd64-xl-sedf blocked test-armhf-armhf-xl-sedf blocked test-amd64-i386-xl-qemut-winxpsp3-vcpus1 blocked test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 blocked test-amd64-i386-xl-winxpsp3-vcpus1 blocked test-amd64-amd64-xl-qemut-winxpsp3 blocked test-amd64-i386-xl-qemut-winxpsp3 blocked test-amd64-amd64-xl-qemuu-winxpsp3 blocked test-amd64-i386-xl-qemuu-winxpsp3 blocked test-amd64-amd64-xl-winxpsp3 blocked test-amd64-i386-xl-winxpsp3 blocked ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/osstest/pub/logs images: /home/osstest/pub/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary broken-step build-armhf-xsm host-install(3) broken-step build-armhf host-install(3) broken-step build-i386-pvops host-install(3) broken-step build-amd64-xsm host-install(3) broken-step build-amd64-pvops host-install(3) broken-step build-amd64 host-install(3) broken-step build-i386 host-install(3) broken-step build-armhf-pvops host-install(3) Not pushing. ------------------------------------------------------------ commit 638b8366200130cc7cf7a026630bc6bfb63b0c4c Author: Alberto Garcia <berto@xxxxxxxxxx> Date: Fri Apr 17 15:44:48 2015 +0300 hmp: fix crash in 'info block -n -v' The image field in BlockDeviceInfo should never be null, however bdrv_block_device_info() is not filling it in. This makes the 'info block -n -v' command crash QEMU. The proper solution is probably to move the relevant code from bdrv_query_info() to bdrv_block_device_info(), but since we're too close to the release for that this simpler workaround solves the crash. Signed-off-by: Alberto Garcia <berto@xxxxxxxxxx> Message-id: 1429274688-8115-1-git-send-email-berto@xxxxxxxxxx Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 87a8adc0876c11a434d3ecdfb10cd797259ddaaa Merge: b6df74c 0ca4f94 Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Fri Apr 17 12:54:46 2015 +0100 Merge remote-tracking branch 'remotes/lalrae/tags/mips-20150417-2' into staging MIPS patches 2015-04-17 Changes: * fix broken fulong2e # gpg: Signature made Fri Apr 17 12:14:37 2015 BST using RSA key ID 0B29DA6B # gpg: Can't check signature: public key not found * remotes/lalrae/tags/mips-20150417-2: mips: fix broken fulong2e machine Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit b6df74c46528646f3163890cf16b74af551c3494 Merge: 993ebe4 6cec43e Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Fri Apr 17 12:37:38 2015 +0100 Merge remote-tracking branch 'remotes/kraxel/tags/pull-fwcfg-20150414-1' into staging fw_cfg: add documentation file (docs/specs/fw_cfg.txt) # gpg: Signature made Tue Apr 14 12:22:20 2015 BST using RSA key ID D3E87138 # gpg: Good signature from "Gerd Hoffmann (work) <kraxel@xxxxxxxxxx>" # gpg: aka "Gerd Hoffmann <gerd@xxxxxxxxxx>" # gpg: aka "Gerd Hoffmann (private) <kraxel@xxxxxxxxx>" * remotes/kraxel/tags/pull-fwcfg-20150414-1: fw_cfg: add documentation file (docs/specs/fw_cfg.txt) Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 0ca4f94195cce77b624edc6d9abcf14a3bf01f06 Author: Paolo Bonzini <pbonzini@xxxxxxxxxx> Date: Thu Apr 16 21:11:23 2015 +0100 mips: fix broken fulong2e machine After commit 5312bd8 the bonito_readl() and bonito_writel() have been accessing incorrect addresses. Consequently QEMU is crashing when trying to boot Linux kernel on fulong2e machine. Cc: qemu-stable@xxxxxxxxxx Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx> Signed-off-by: Leon Alrae <leon.alrae@xxxxxxxxxx> commit 993ebe4a0be9aa4e4821818a81fab00b1ab1a79a Author: Mark Cave-Ayland <mark.cave-ayland@xxxxxxxxxxxx> Date: Fri Apr 17 08:16:49 2015 +0100 target-ppc: don't invalidate msr MSR_HVB bit in cpu_post_load The invalidation code introduced in commit 2360b works by inverting most bits of env->msr to ensure that hreg_store_msr() will forcibly update the CPU env state to reflect the new msr value post-migration. Unfortunately hreg_store_msr() is called with alter_hv set to 0 which preserves the MSR_HVB state from the CPU env which is now the opposite value to what it should be. Ensure that we don't invalidate the msr MSR_HVB bit during cpu_post_load so that the correct value is restored. This fixes suspend/resume for PPC64. Reported-by: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@xxxxxxxxxxxx> Reviewed-by: Alexander Graf <agraf@xxxxxxx> Message-id: 1429255009-12751-1-git-send-email-mark.cave-ayland@xxxxxxxxxxxx Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 6cec43e178cde38a3eac43a2cd741ce741b10f36 Author: Gabriel L. Somlo <somlo@xxxxxxx> Date: Thu Apr 9 10:40:01 2015 -0400 fw_cfg: add documentation file (docs/specs/fw_cfg.txt) This document covers the guest-side hardware interface, as well as the host-side programming API of QEMU's firmware configuration (fw_cfg) device. Signed-off-by: Jordan Justen <jordan.l.justen@xxxxxxxxx> Signed-off-by: Gabriel Somlo <somlo@xxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> Signed-off-by: Gerd Hoffmann <kraxel@xxxxxxxxxx> commit b8df9208f357d2b36e1b19634aea973618dc7ba8 Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Mon Apr 13 17:35:44 2015 +0100 Update version for v2.3.0-rc3 release Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit ae6e8ef11e6cb43ec83a5846e8f3b266834cf280 Author: Peter Maydell <peter.maydell@xxxxxxxxxx> Date: Fri Apr 10 13:58:01 2015 +0100 Revert seccomp tests that allow it to be used on non-x86 architectures Unfortunately it turns out that libseccomp 2.2 still does not work correctly on non-x86 architectures; return to the previous configure setup of insisting on libseccomp 2.1 or better and i386/x86_64 and disabling seccomp support in all other situations. This reverts the two commits: * "seccomp: libseccomp version varying according to arch" (commit 896848f0d3e2393905845ef2b244bb2601f9df0c) * "seccomp: update libseccomp version and remove arch restriction" (commit 8e27fc200457e3f2473d0069263774d4ba17bd85) Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> Message-id: 1428670681-23032-1-git-send-email-peter.maydell@xxxxxxxxxx commit 4d0ecde44ae6dab3aa9d10c23e61d9d43789731a Author: Thomas Huth <thuth@xxxxxxxxxx> Date: Thu Apr 9 15:32:45 2015 +0200 pci: Fix crash with illegal "-net nic, model=xxx" option Current QEMU crashes when specifying an illegal model with the "-net nic,model=xxx" option, e.g.: $ qemu-system-x86_64 -net nic,model=n/a qemu-system-x86_64: Unsupported NIC model: n/a Program received signal SIGSEGV, Segmentation fault. The gdb backtrace looks like this: 0x0000555555965fe0 in error_get_pretty (err=0x0) at util/error.c:152 152 return err->msg; (gdb) bt 0 0x0000555555965fe0 in error_get_pretty (err=0x0) at util/error.c:152 1 0x0000555555965ffd in error_report_err (err=0x0) at util/error.c:157 2 0x0000555555809c90 in pci_nic_init_nofail (nd=0x555555e49860 <nd_table>, rootbus=0x5555564409b0, default_model=0x55555598c37b "e1000", default_devaddr=0x0) at hw/pci/pci.c:1663 3 0x0000555555691e42 in pc_nic_init (isa_bus=0x555556f71900, pci_bus=0x5555564409b0) at hw/i386/pc.c:1506 4 0x000055555569396b in pc_init1 (machine=0x5555562abbf0, pci_enabled=1, kvmclock_enabled=1) at hw/i386/pc_piix.c:248 5 0x0000555555693d27 in pc_init_pci (machine=0x5555562abbf0) at hw/i386/pc_piix.c:310 6 0x000055555572ddf5 in main (argc=3, argv=0x7fffffffe018, envp=0x7fffffffe038) at vl.c:4226 The problem is that pci_nic_init_nofail() does not check whether the err parameter from pci_nic_init has been set up and thus passes a NULL pointer to error_report_err(). Fix it by correctly checking the err parameter. Signed-off-by: Thomas Huth <thuth@xxxxxxxxxx> Reviewed-by: Michael S. Tsirkin <mst@xxxxxxxxxx> Reviewed-by: Jason Wang <jasowang@xxxxxxxxxx> Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit 342b0711cd62ddc08d334d879eac57b68f925fd5 Author: Andreas Färber <afaerber@xxxxxxx> Date: Fri Apr 10 16:37:56 2015 +0200 stm32f205: Fix SoC type name The type name for the SoC device, unlike those of its sub-devices, did not follow the QOM naming conventions. While the usage is internal only, this is exposed through QMP and HMP, so fix it before release. Cc: Alistair Francis <alistair.francis@xxxxxxxxxx> Signed-off-by: Andreas Färber <afaerber@xxxxxxx> Reviewed-by: Alistair Francis <alistair@xxxxxxxxxxxxx> Message-id: 1428676676-23056-1-git-send-email-afaerber@xxxxxxx Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx> commit c0c8584142a13e728178e51f2477c23a84ce74b4 Author: Dirk Müller <dirk@xxxxxxxx> Date: Sat Apr 4 14:15:10 2015 +0200 cris: memory: Replace memory_region_init_ram with memory_region_allocate_system_memory Commit 0b183fc871:"memory: move mem_path handling to memory_region_allocate_system_memory" split memory_region_init_ram and memory_region_init_ram_from_file. Also it moved mem-path handling a step up from memory_region_init_ram to memory_region_allocate_system_memory. Therefore for any board that uses memory_region_init_ram directly, -mem-path is not supported. Fix this by replacing memory_region_init_ram with memory_region_allocate_system_memory. Tested-by: Edgar E. Iglesias <edgar.iglesias@xxxxxxxxxx> Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xxxxxxxxxx> Cc: Edgar E. Iglesias <edgar.iglesias@xxxxxxxxx> Signed-off-by: Dirk Mueller <dmueller@xxxxxxxx> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |