|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [libvirt test] 144345: regressions - FAIL
flight 144345 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/144345/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-libvirt-qcow2 15 guest-start/debian.repeat fail REGR. vs. 144304 Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 14 saverestore-support-check fail like 144304 test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 144304 test-amd64-amd64-libvirt 13 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-i386-libvirt 13 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-arm64-arm64-libvirt 13 migrate-support-check fail never pass test-arm64-arm64-libvirt 14 saverestore-support-check fail never pass test-arm64-arm64-libvirt-xsm 13 migrate-support-check fail never pass test-arm64-arm64-libvirt-xsm 14 saverestore-support-check fail never pass test-arm64-arm64-libvirt-qcow2 12 migrate-support-check fail never pass test-arm64-arm64-libvirt-qcow2 13 saverestore-support-check fail never pass test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 13 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass version targeted for testing: libvirt 83254ea750b476b5041c838a583d9ea3f632a6a2 baseline version: libvirt 9d6920bd7de3f92be1894790adeb689060ab25eb Last test of basis 144304 2019-11-26 04:19:14 Z 2 days Failing since 144318 2019-11-27 04:19:28 Z 1 days 2 attempts Testing same since 144345 2019-11-28 04:19:33 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Daniel P. Berrangé <berrange@xxxxxxxxxx> Michal Privoznik <mprivozn@xxxxxxxxxx> Peter Krempa <pkrempa@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm pass build-i386-xsm pass build-amd64 pass build-arm64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-arm64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-arm64-pvops pass 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 pass test-arm64-arm64-libvirt-xsm pass test-amd64-i386-libvirt-xsm pass test-amd64-amd64-libvirt pass test-arm64-arm64-libvirt pass 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 fail 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 Not pushing. ------------------------------------------------------------ commit 83254ea750b476b5041c838a583d9ea3f632a6a2 Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Wed Nov 27 11:19:47 2019 +0100 news: Update for 5.10.0 release Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx> commit d310b0869753a860e499c66823fb4fe427d46af8 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Nov 26 15:13:57 2019 +0100 qemu: blockjob: Finish handling job with broken data Now that we have a separate job type which will not trigger normal code paths for terminating job we can remove the ad-hoc handling. This possibly fixes the issue of a broken job inheriting the disk and then finishing in which case we'd not detach the backing chain. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit e67e8c545a88b1ee3da0f591da96e6d4c57046b0 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Nov 26 14:55:05 2019 +0100 qemu: blockjob: Introduce "broken" block job type To better track jobs we couldn't parse let's introduce a new job type which will clarify semantics internally in few places. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit 2624c6d2d2be96a94c1678b83fde407ffb3aa49f Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Nov 26 13:39:18 2019 +0100 qemu: blockjob: Separate clearing of per-job data We will need to clear per-job type data when we will be marking a blockjob as broken in the new way. Extract the code for future reuse. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit 0cb3061943a891dc5c5429ac6a332eb8b2c14300 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Nov 26 14:29:42 2019 +0100 qemu: blockjob: Don't stop processing the finished job early Both failure to refresh and to dismiss the job are very unlikely but if they happen there's not much we can do about the blockjob. The concluded job handlers treat it as if the job failed if we don't update the state to 'QEMU_BLOCKJOB_STATE_COMPLETED' which is probably the safest thing to do here. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit 5b29c7dc276da9d36eae4361d20d3095db262baa Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Nov 26 14:16:37 2019 +0100 qemu: blockjob: Mark job with broken data but tracked by qemu as reconnected Otherwise it would get dropped later on as untracked despite us knowing about it. Additionally since we cancelled it we must wait to dismiss it which would not be possible if we unregister it. This also opened a window for a race condition since the job state change event of the just-cancelled job might be delivered prior to us unregistering the job in which case everything would work properly. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit f15d4cb1c869ff691b2d6cddbe8463be28d526e1 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Nov 26 14:14:54 2019 +0100 qemu: blockjob: Log blockjobs which are dropped when untracked by qemu Since we don't know what happened to the job we can't do much about it but we can at least log that this happened. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit 8622498f6e42d29140f5ca63393ef29e2ffc0d51 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Nov 26 13:16:36 2019 +0100 qemu: blockjob: Fix deadlock when terminating job with invalid data We must exit the monitor prior to refusing other work, otherwise the VM object will become unusable. This bug was introduced in commit v5.5.0-244-gc412383796 but thankfully the code path was not excercised without QEMU_CAPS_BLOCKDEV. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit ccde9ca1f4fa5c2f1a3a2fac53661c27faeaea1c Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Nov 26 13:04:30 2019 +0100 qemu: process: Move block job refresh after async job recovery Block jobs may be members of async jobs so it makes more sense to refresh block job state after we do steps for async job recovery. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit a887da529cd2d16f7fa71dabb1bae90f6a2da31b Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Nov 26 09:28:22 2019 +0100 qemu: blockjob: Properly propagate cancellation of blockjobs qemu returns an error message in the job statistics even if the job was cancelled to emphasize it was not successful. Libvirt didn't properly transform it into QEMU_BLOCKJOB_STATE_CANCELLED though. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit 01270a9a5fb0670b8d058aa4dea0db5c268642d3 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Mon Nov 25 21:28:14 2019 +0100 qemu: monitor: Finish implementation of infrastructure for 'query-jobs' Commit ed56851f1bc6f5 didn't wire up fetching of the statistics for the job which are reported by 'query-jobs'. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit 27660f7990f292bbe3c8a59eab9fa0fa085971b4 Author: Daniel P. Berrangé <berrange@xxxxxxxxxx> Date: Tue Nov 26 16:29:47 2019 +0000 util: whitelist Oracle ACFS as a shared filesystem The magic number is taken from the coreutils stat.c file since there is no constant for it in normal system headers. Reviewed-by: Daniel Henrique Barboza <danielhb413@xxxxxxxxx> Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> commit 6881ef2e4eb53659a89830204ce434a9647e2001 Author: Daniel P. Berrangé <berrange@xxxxxxxxxx> Date: Tue Nov 26 15:59:13 2019 +0000 libxl: fix typo in error message Reviewed-by: Fabiano Fidêncio <fidencio@xxxxxxxxxx> Reviewed-by: Daniel Henrique Barboza <danielhb413@xxxxxxxxx> Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> commit a10eb613404fedb4ce44ec47848710fdb3d7a91d Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Wed Nov 27 13:40:14 2019 +0100 Revert "qemu: Don't repeat virDomainObjEndAPI in qemuDomainBlockPull" This reverts commit 421c9550f5446729b513ee50f5c44e6f6969b5a2 qemuDomainBlockPullCommon calls virDomainObjEndAPI internally so the original commit made us shed two references of @vm instead of one getting us into a premature free of @vm. This is not a straight revert as qemuDomainBlockPull was modified meanwhile. I've also added a warning comment that @vm is consumed. https://bugzilla.redhat.com/show_bug.cgi?id=1777230 Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx> commit c8579871a980e7cd41df50afad62e9c3183534c6 Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Tue Nov 26 15:28:22 2019 +0100 all: don't wait for driver lock during startup There are two daemons that wait for acquiring their pid files: virtnetworkd and virtstoraged. This is undesirable as the idea is to quit early if unable to acquire the pid file. Fixes: v5.6.0-rc1~207. Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx> Reviewed-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> commit 3b9359cd44b5a97fe5d670ee33ff13c4bf297ea8 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Mon Nov 25 16:33:53 2019 +0100 check-symfile: Use pythonesque string formatting instead of perl Commit d30a1ad0443 translated the symbol file checker from perl to python by doing a literal translation in most cases. Unfortunately one string formatting operation was not really translated into python leaving users with non-helpful error: 'Symbol $1 is listed twice' Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> Reviewed-by: Erik Skultety <eskultet@xxxxxxxxxx> Reviewed-by: Michal Privoznik <mprivozn@xxxxxxxxxx> _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |