aboutsummaryrefslogtreecommitdiff
path: root/block
diff options
context:
space:
mode:
authorFiona Ebner <f.ebner@proxmox.com>2023-08-17 13:25:38 +0200
committerKevin Wolf <kwolf@redhat.com>2023-09-08 17:03:09 +0200
commit65c23ef1e4197c53d3836906895062307e48a6c5 (patch)
tree7ad1b37fc71336a9626e9acdea798c4d6268c1cf /block
parent3c2c599c79eea9cebd7280140a5901fe3734e94e (diff)
downloadqemu-65c23ef1e4197c53d3836906895062307e48a6c5.zip
qemu-65c23ef1e4197c53d3836906895062307e48a6c5.tar.gz
qemu-65c23ef1e4197c53d3836906895062307e48a6c5.tar.bz2
iotests: adapt test output for new qemu_cleanup() behavior
Since commit ca2a5e630d ("qemu_cleanup: begin drained section after vm_shutdown()"), there will be an additional pause for jobs during qemu_cleanup(). The reason is that the bdrv_drain_all() call in do_vm_stop() is not inside the drained section used by qemu_cleanup() anymore. I.e., there is a second drained section now that ends before the final one in qemu_cleanup() starts. Thus, job_pause() is called twice during cleanup (via child_job_drained_begin()). Test 185 needs to be adapted directly too, because it waits for a specific number of JOB_STATUS_CHANGE events before the BLOCK_JOB_CANCELLED event. Reported-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com> Message-ID: <20230817112538.255111-1-f.ebner@proxmox.com> Reviewed-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions