|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [libvirt test] 106006: trouble: blocked/broken/fail/pass
flight 106006 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/106006/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-libvirt-xsm 3 host-install(3) broken REGR. vs. 105973 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-libvirt-xsm 13 saverestore-support-check fail like 105973 test-armhf-armhf-libvirt 13 saverestore-support-check fail like 105973 test-armhf-armhf-libvirt-raw 12 saverestore-support-check fail like 105973 Tests which did not succeed, but are not blocking: test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a build-arm64-libvirt 1 build-check(1) blocked n/a test-arm64-arm64-libvirt-qcow2 1 build-check(1) blocked n/a test-arm64-arm64-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass build-arm64 5 xen-build fail never pass build-arm64-xsm 5 xen-build fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass build-arm64-pvops 5 kernel-build fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass version targeted for testing: libvirt ff029e4434408b7fa2838e07981368394a201d49 baseline version: libvirt 5ad03b9db2186d5b1d09f33e5ab0daa683054675 Last test of basis 105973 2017-02-22 04:20:09 Z 1 days Testing same since 106006 2017-02-23 04:20:53 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrea Bolognani <abologna@xxxxxxxxxx> Jiri Denemark <jdenemar@xxxxxxxxxx> John Ferlan <jferlan@xxxxxxxxxx> Michal Privoznik <mprivozn@xxxxxxxxxx> Peter Krempa <pkrempa@xxxxxxxxxx> Tomáš Golembiovský <tgolembi@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm fail build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-arm64 fail build-armhf pass build-i386 pass build-amd64-libvirt pass build-arm64-libvirt blocked build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-arm64-pvops fail build-armhf-pvops pass build-i386-pvops pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-xsm broken test-arm64-arm64-libvirt-xsm blocked test-armhf-armhf-libvirt-xsm pass test-amd64-i386-libvirt-xsm pass test-amd64-amd64-libvirt pass test-arm64-arm64-libvirt blocked test-armhf-armhf-libvirt pass test-amd64-i386-libvirt pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-arm64-arm64-libvirt-qcow2 blocked test-armhf-armhf-libvirt-raw pass test-amd64-amd64-libvirt-vhd 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-amd64-libvirt-xsm host-install(3) Not pushing. ------------------------------------------------------------ commit ff029e4434408b7fa2838e07981368394a201d49 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Feb 9 16:34:52 2017 -0500 virsh: Alter formatting a bit for output of domstats fields Alter the formatting of each line to not give the appearance of one long run-on sentence and to be consistent between the various elements of collected/displayed data. The formatting should fit within the 80 character display. This removes the need for commas at the end of each line. commit 011d546504e8b36c51b69d2f556ccdbcee975bed Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Tue Feb 21 13:16:52 2017 +0100 qemu: Allow multiple bridges when pci-bridges is not available qemuDomainAssignPCIAddresses() hardcoded the assumption that the only way to support devices on a non-zero bus is to add one or more pci-bridges; however, since we now support a large selection of PCI controllers that can be used instead, the assumption is no longer true. Moreover, this check was always redundant, because the only sensible time to check for the availability of pci-bridge is when building the QEMU command line, and such a check is of course already in place. In fact, there were *two* such checks, but since one of the two was relying on the incorrect assumption explained above, and it was redundant anyway, it has been dropped. commit d4393c42934dd1960c022f77834f3987eb8de5e7 Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Tue Feb 21 14:30:39 2017 +0100 tests: Reduce usage of legacy PCI controllers on PCIe machines Up until a while ago, libvirt would automatically add a legacy PCI controllers combo (dmi-to-pci-bridge + pci-bridge) to any PCIe machine type (x86_64/q35 and aarch64/virt). As a result, a number of input and output files in the test suite ended up containing the legacy PCI controllers, even though they are not needed or in any way relevant to the feature being tested. Get rid of most of the occurrences. Most of the time, this just means removing the controllers from the input file and regenerating the output files; in a few instances, some minor tweaking is performed on the input file, most notably removing the memory balloon: as memory balloon support was not the scope of the test being changed, there is no loss of test coverage from doing so. Several occurrences of the legacy PCI controllers remain in the test suite, both because removing their usage would have required even more tweaking, and because we still want to have coverage of this perfectly valid combination. commit 77edbf512701f239b406779811d6fd8bfb9156d9 Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Tue Feb 21 20:13:47 2017 +0100 conf: Make switch statements more strict When switching over the values in the virDomainControllerModelPCI enumeration, make sure the proper cast is in place so that the compiler can warn us when the coverage is not exaustive. For the same reason, remove the 'default' case from one of the existing switch statements. commit 50d3595390bf573e6567a698d44ef4873de00140 Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Tue Feb 21 20:13:35 2017 +0100 qemu: Make switch statements more strict When switching over the values in the virDomainControllerModelPCI enumeration, make sure the proper cast is in place so that the compiler can warn us when the coverage is not exaustive. For the same reason, fold some unstructured checks (performed by comparing directly against some values in the enumeration) inside an existing switch statement. commit c6a0fb8e71bc44745332a61ce73959a84e93f9c4 Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Mon Feb 20 15:56:18 2017 +0100 conf: Remove dead code The switch in virDomainPCIControllerModelToConnectType() had some code that, while techically part of the _PCIE_SWITCH_DOWNSTREAM_PORT case, was in fact dead due to the early return. Get rid of the dead code, and fix the inaccurate function description while at it. commit 75ba06e44afd60c358aa08b9bbf75d35d0f7ec23 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Feb 16 14:59:06 2017 -0500 qemu: Rename qemuAliasTLSObjFromChardevAlias It's not really 'Chardev' specific - we can reuse this for other objects. Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit 82ddd0b1550efa899f1bded14adc66410648d120 Author: Jiri Denemark <jdenemar@xxxxxxxxxx> Date: Thu Feb 2 22:04:25 2017 +0100 cpu: Use virCPUData.arch in cpuDecode virCPUDef.arch is not required to be filled in for guest CPU definitions. It doesn't make sense to artificially mandate it to be set when cpuDecode is called especially when virCPUData.arch passed to cpuDecode already contains the architecture. Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit 4cd9545d89cf12b386f1e9d10c1b0721fa3f3e94 Author: Jiri Denemark <jdenemar@xxxxxxxxxx> Date: Thu Feb 2 12:09:52 2017 +0100 cpu: Introduce virCPUDataNew Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit e2f7138af48c477f2ef82579786ecbe040bb798f Author: Jiri Denemark <jdenemar@xxxxxxxxxx> Date: Fri Jan 13 18:42:57 2017 +0100 qemu: Introduce virQEMUCapsFormatHostCPUModelInfo The CPU model info formating code in virQEMUCapsFormatCache will get more complicated soon. Separating the code in virQEMUCapsFormatHostCPUModelInfo will make the result easier to read. Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit 5c6fc9d641252525d65374a25f00a0e6f6e7c8cd Author: Jiri Denemark <jdenemar@xxxxxxxxxx> Date: Wed Jan 18 14:05:26 2017 +0100 qemu: Skip virQEMUCapsCPUFilterFeatures on non-x86 CPUs All features the function is currently supposed to filter out are specific to x86_64. We should avoid removing them on other architectures. It seems to be quite unlikely other achitectures would use the same names, but one can never be sure. Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit c49629109b4a60b3990a2c5a1db295f131d7f30e Author: Jiri Denemark <jdenemar@xxxxxxxxxx> Date: Wed Feb 15 09:24:16 2017 +0100 docs: Fix since statement in host-model documentation Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit 9b521dbc0891767add23d57af6acd7ef721a917c Author: Jiri Denemark <jdenemar@xxxxxxxxxx> Date: Tue Feb 14 23:32:24 2017 +0100 docs: Drop obsolete statement about CPU modes and migration The guest CPU definition has always been updated automatically during migration. And currently we just transform any host-model CPU into a custom one when a domain starts. Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit e4c6d4ae557a5de3a4b9a7e789df0e8f1d140557 Author: Tomáš Golembiovský <tgolembi@xxxxxxxxxx> Date: Mon Feb 13 23:53:43 2017 +0100 util: storage: add JSON backing volume parser 'raw' block driver The 'raw' block driver in Qemu is not directly interesting from libvirt's perspective, but it can be layered above some other block drivers and this may be interesting for the user. The patch adds support for the 'raw' block driver. The driver is treated simply as a pass-through and child driver in JSON is queried to get the necessary information. Signed-off-by: Tomáš Golembiovský <tgolembi@xxxxxxxxxx> commit cb4adb43d6bf6944cbea8a128e134545d101d29c Author: Tomáš Golembiovský <tgolembi@xxxxxxxxxx> Date: Mon Feb 13 23:53:42 2017 +0100 util: storage: split function for JSON backing volume parsing in two Split virStorageSourceParseBackingJSON into two functions so that the core can be reused by other functions. The new function called virStorageSourceParseBackingJSONInternal accepts virJSONValuePtr. Signed-off-by: Tomáš Golembiovský <tgolembi@xxxxxxxxxx> commit b26401fab360e5bdedca1d954f57ddbe2c18f781 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Wed Feb 8 17:25:16 2017 +0100 news: Mention storage driver split commit 27c8e36d60c7f2d7abf105207546f87e15256c45 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Wed Feb 8 09:20:21 2017 +0100 spec: Modularize the storage driver Create a new set of sub-packages containing the new storage driver modules so that certain heavy-weight backends (gluster, rbd) can be installed separately only if required. To keep backward compatibility the 'libvirt-driver-storage' package will be turned into a virtual package pulling in all the new storage backend sub-packages. The storage driver module will be moved into libvirt-driver-storage-core including the filesystem backend which is mandatory. This then allows to make libvirt-daemon-driver-qemu depend only on the core of the storage driver. All other meta-packages still depend on the full storage driver and thus pull in all the backends. commit 93a3f516ee5453f9fbea63a2e9d1495fc369d226 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Feb 7 18:58:39 2017 +0100 tests: drivermodule: Make sure that all compiled storage backends can be loaded Add a new storage driver registration function that will force the backend code to fail if any of the storage backend modules can't be loaded. This will make sure that they work and are present. commit 0a6d3e51b40cfd0628649f985975b0d2be00b8f7 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Feb 7 19:40:29 2017 +0100 storage: Turn storage backends into dynamic modules If driver modules are enabled turn storage driver backends into dynamically loadable objects. This will allow greater modularity for binary distributions, where heavyweight dependencies as rbd and gluster can be avoided by selecting only a subset of drivers if the rest is not necessary. The storage modules are installed into 'LIBDIR/libvirt/storage-backend/' and users can override the location by using 'LIBVIRT_STORAGE_BACKEND_DIR' environment variable. rpm based distros will at this point install all the backends when libvirt-daemon-driver-storage package is installed. commit 4fb105f681aee6ddae994410b1bc23de29124d6c Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Feb 21 10:16:04 2017 +0100 spec: Don't check for storage driver backends in configure script Explicitly enable --with-storage-scsi and disable --without-storage-zfs and --without-storage-vstorage so that the configure script doesn't check for them. Note that --with-storage-dir is enabled by default. commit 0888cb6ab4a8282dd4a67a01be8f2fda28661bfd Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Tue Feb 21 17:24:17 2017 +0100 conf: Don't accept dummy values for <memoryBacking/> attributes Our virSomeEnumTypeFromString() functions return either the value of item from the enum or -1 on error. Usually however the value 0 means 'this value is not set in the domain XML, use some sensible default'. Therefore, we don't accept corresponding string in domain XML, for instance: <memoryBacking> <source mode="none"/> <access mode="default"/> <allocation mode="none"/> </memoryBacking> should be rejected as invalid XML. Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |