|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [libvirt test] 175917: regressions - trouble: blocked/broken/fail/pass
flight 175917 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/175917/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 <job status> broken build-amd64-pvops <job status> broken build-amd64-xsm <job status> broken build-arm64 <job status> broken build-arm64-pvops <job status> broken build-arm64-xsm <job status> broken build-armhf <job status> broken build-armhf-pvops <job status> broken build-armhf 4 host-install(4) broken REGR. vs. 175736 build-armhf-pvops 5 host-build-prep fail REGR. vs. 175736 build-amd64 5 host-build-prep fail REGR. vs. 175736 build-amd64-xsm 5 host-build-prep fail REGR. vs. 175736 build-arm64 5 host-build-prep fail REGR. vs. 175736 build-amd64-pvops 5 host-build-prep fail REGR. vs. 175736 build-arm64-pvops 5 host-build-prep fail REGR. vs. 175736 build-arm64-xsm 5 host-build-prep fail REGR. vs. 175736 build-i386-xsm 6 xen-build fail REGR. vs. 175736 build-i386 6 xen-build fail REGR. vs. 175736 Tests which did not succeed, but are not blocking: build-amd64-libvirt 1 build-check(1) blocked n/a build-arm64-libvirt 1 build-check(1) blocked n/a build-armhf-libvirt 1 build-check(1) blocked n/a build-i386-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-libvirt-pair 1 build-check(1) blocked n/a test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a test-amd64-amd64-libvirt-vhd 1 build-check(1) blocked n/a test-amd64-amd64-libvirt-xsm 1 build-check(1) blocked n/a test-amd64-i386-libvirt 1 build-check(1) blocked n/a test-amd64-i386-libvirt-pair 1 build-check(1) blocked n/a test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a test-amd64-i386-libvirt-raw 1 build-check(1) blocked n/a test-amd64-i386-libvirt-xsm 1 build-check(1) blocked n/a test-arm64-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-raw 1 build-check(1) blocked n/a test-armhf-armhf-libvirt-raw 1 build-check(1) blocked n/a test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a test-armhf-armhf-libvirt 1 build-check(1) blocked n/a test-armhf-armhf-libvirt-qcow2 1 build-check(1) blocked n/a version targeted for testing: libvirt 46aee2a9255adf842ab44a9292acb46189a726f7 baseline version: libvirt 12a3bee3899cdba8b637a7286f24ade1214b6420 Last test of basis 175736 2023-01-12 04:18:57 Z 4 days Testing same since 175917 2023-01-16 04:18:43 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Anton Fadeev <anton.fadeev@xxxxxxxxxxx> antonios-f <anton.fadeev@xxxxxxxxxxx> Erik Skultety <eskultet@xxxxxxxxxx> Han Han <hhan@xxxxxxxxxx> Ján Tomko <jtomko@xxxxxxxxxx> Laine Stump <laine@xxxxxxxxxx> Michal Privoznik <mprivozn@xxxxxxxxxx> Peter Krempa <pkrempa@xxxxxxxxxx> Yuri Chornoivan <yurchor@xxxxxxx> 김인수 <simmon@xxxxxxxxx> jobs: build-amd64-xsm broken build-arm64-xsm broken build-i386-xsm fail build-amd64 broken build-arm64 broken build-armhf broken build-i386 fail build-amd64-libvirt blocked build-arm64-libvirt blocked build-armhf-libvirt blocked build-i386-libvirt blocked build-amd64-pvops broken build-arm64-pvops broken build-armhf-pvops broken build-i386-pvops pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm blocked test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm blocked test-amd64-amd64-libvirt-xsm blocked test-arm64-arm64-libvirt-xsm blocked test-amd64-i386-libvirt-xsm blocked test-amd64-amd64-libvirt blocked test-arm64-arm64-libvirt blocked test-armhf-armhf-libvirt blocked test-amd64-i386-libvirt blocked test-amd64-amd64-libvirt-pair blocked test-amd64-i386-libvirt-pair blocked test-arm64-arm64-libvirt-qcow2 blocked test-armhf-armhf-libvirt-qcow2 blocked test-arm64-arm64-libvirt-raw blocked test-armhf-armhf-libvirt-raw blocked test-amd64-i386-libvirt-raw blocked test-amd64-amd64-libvirt-vhd blocked ------------------------------------------------------------ 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-job build-amd64 broken broken-job build-amd64-pvops broken broken-job build-amd64-xsm broken broken-job build-arm64 broken broken-job build-arm64-pvops broken broken-job build-arm64-xsm broken broken-job build-armhf broken broken-job build-armhf-pvops broken broken-step build-armhf host-install(4) Not pushing. ------------------------------------------------------------ commit 46aee2a9255adf842ab44a9292acb46189a726f7 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Fri Jan 13 10:24:38 2023 +0100 NEWS: Document virDomainFDAssociate and NULL dereference in virXMLPropStringRequired Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx> commit 6ce7cebea32148372ebd567ba25b380d8ab49781 Author: Laine Stump <laine@xxxxxxxxxx> Date: Thu Jan 12 23:42:18 2023 -0500 tests: remove unused qemu .args file net-user-passt.args was generated early during testing of the passt qemu commandline, when qemuxml2argvtest was using DO_TEST("net-user-passt"). This was later changed to DO_TEST_CAPS_LATEST(), so the file net-user-passt.x86_64-latest.args is used instead, but the original (now unused) test file was accidentally added to the original patch. This patch removes it. Signed-off-by: Laine Stump <laine@xxxxxxxxxx> Reviewed-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit a2042a45165938f2d747edd17f12ca03eea51791 Author: Laine Stump <laine@xxxxxxxxxx> Date: Thu Jan 12 23:42:17 2023 -0500 qemu: remove commented-out option in passt qemu commandline setup This commented-out option was pointed out by jtomko during review, but I missed taking it out when addressing his comments. Signed-off-by: Laine Stump <laine@xxxxxxxxxx> Reviewed-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit 3592b81c4c717f01f34362e0b578989f9f93676f Author: Laine Stump <laine@xxxxxxxxxx> Date: Thu Jan 12 23:42:16 2023 -0500 conf: remove <backend upstream='xxx'/> attribute This attribute was added to support setting the --interface option for passt, but in a post-push/pre-9.0-release review, danpb pointed out that it would be better to use the existing <source dev='xxx'/> attribute to set --interface rather than creating a new attribute (in the wrong place). So we remove backend/upstream, and change the passt commandline creation to grab the name for --interface from source/dev. Signed-off-by: Laine Stump <laine@xxxxxxxxxx> Reviewed-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit 8ff8fe3f8a7bb67a150c7f4801c2df5ef743aa8f Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Thu Jan 5 09:51:07 2023 +0100 qemuBuildThreadContextProps: Generate ThreadContext less frequently Currently, the ThreadContext object is generated whenever we see .host-nodes attribute for a memory-backend-* object. The idea was that when the backend is pinned to a specific set of host NUMA nodes, then the allocation could be happening on CPUs from those nodes too. But this may not be always possible. Users might configure their guests in such way that vCPUs and corresponding guest NUMA nodes are on different host NUMA nodes than emulator thread. In this case, ThreadContext won't work, because ThreadContext objects live in context of the emulator thread (vCPU threads are moved around by us later, when emulator thread finished its setup and spawned vCPU threads - see qemuProcessSetupVcpus()). Therefore, memory allocation is done by emulator thread which is pinned to a subset of host NUMA nodes, but tries to create a ThreadContext object with a disjoint subset of host NUMA nodes, which fails. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2154750 Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx> commit ed6b8a30b90807d5a4d6bc0a5d0ec99fd5f040ff Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Tue Jan 3 10:29:01 2023 +0100 security_selinux: Set and restore /dev/sgx_* labels For SGX type of memory, QEMU needs to open and talk to /dev/sgx_vepc and /dev/sgx_provision files. But we do not set nor restore SELinux labels on these files when starting a guest. Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx> commit a50e6f649b49ee89e25a4afba4ad8d537014e33f Author: Ján Tomko <jtomko@xxxxxxxxxx> Date: Wed Jan 11 16:04:23 2023 +0100 NEWS: document external swtpm backend addition Signed-off-by: Ján Tomko <jtomko@xxxxxxxxxx> Reviewed-by: Andrea Bolognani <abologna@xxxxxxxxxx> commit 08e3bf0b6f8b9612bb2fc02e7d30fc75d6b10daf Author: 김인수 <simmon@xxxxxxxxx> Date: Thu Jan 12 09:59:36 2023 +0100 Translated using Weblate (Korean) Currently translated at 99.5% (10362 of 10405 strings) Translation: libvirt/libvirt Translate-URL: https://translate.fedoraproject.org/projects/libvirt/libvirt/ko/ Co-authored-by: 김인수 <simmon@xxxxxxxxx> Signed-off-by: 김인수 <simmon@xxxxxxxxx> commit d07a7793dab57d49b3dec166a62f8e82137e17a9 Author: Yuri Chornoivan <yurchor@xxxxxxx> Date: Thu Jan 12 09:59:36 2023 +0100 Translated using Weblate (Ukrainian) Currently translated at 100.0% (10405 of 10405 strings) Translation: libvirt/libvirt Translate-URL: https://translate.fedoraproject.org/projects/libvirt/libvirt/uk/ Co-authored-by: Yuri Chornoivan <yurchor@xxxxxxx> Signed-off-by: Yuri Chornoivan <yurchor@xxxxxxx> commit 9233f0fa8c8e031197c647f7bc980dee45283641 Author: antonios-f <anton.fadeev@xxxxxxxxxxx> Date: Thu Nov 17 09:53:23 2022 +0000 src/util/vircgroupv2.c: interpret neg quota as "max" Because of kernel doesn't allow passing negative values to cpu.max as quota, it's needing to convert negative values to "max" token. Signed-off-by: Anton Fadeev <anton.fadeev@xxxxxxxxxxx> Reviewed-by: Pavel Hrdina <phrdina@xxxxxxxxxx> commit f41d1a2e751549c8817326740c5761a0775a1fb6 Author: Han Han <hhan@xxxxxxxxxx> Date: Thu Jan 12 12:10:21 2023 +0800 docs: drvqemu: Fix a typo Fixes: a677ea928a65fceb1463e14044b23d7fba6acd3d Signed-off-by: Han Han <hhan@xxxxxxxxxx> Reviewed-by: Andrea Bolognani <abologna@xxxxxxxxxx> commit ad00beffa6f3ca8b7c09e454a70a8281fa656524 Author: Erik Skultety <eskultet@xxxxxxxxxx> Date: Thu Jan 12 07:57:58 2023 +0100 ci: integration: Set an expiration on logs artifacts The default expiry time is 30 days. Since the RPM artifacts coming from the previous pipeline stages are set to expire in 1 day we can set the failed integration job log artifacts to the same value. The sentiment here is that if an integration job legitimately failed (i.e. not with an infrastructure failure) unless it was fixed in the meantime it will fail the next day with the scheduled pipeline again, meaning, that even if the older log artifacts are removed, they'll be immediately replaced with fresh ones. Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx> Reviewed-by: Daniel P. Berrangé <berrange@xxxxxxxxxx>
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |