]> git.ipfire.org Git - thirdparty/qemu.git/commit
iotests: Make 144 deterministic again
authorKevin Wolf <kwolf@redhat.com>
Fri, 9 Feb 2024 17:31:03 +0000 (18:31 +0100)
committerMichael Tokarev <mjt@tls.msk.ru>
Fri, 16 Feb 2024 11:28:23 +0000 (14:28 +0300)
commitfc39dc294cdf2117d7b41503d3e37960a6302068
tree0341a0f1820546b43e42d173b6944a42df04f6de
parent688450c4a76cedd93e1f464c3e07a573b8add411
iotests: Make 144 deterministic again

Since commit effd60c8 changed how QMP commands are processed, the order
of the block-commit return value and job events in iotests 144 wasn't
fixed and more and caused the test to fail intermittently.

Change the test to cache events first and then print them in a
predefined order.

Waiting three times for JOB_STATUS_CHANGE is a bit uglier than just
waiting for the JOB_STATUS_CHANGE that has "status": "ready", but the
tooling we have doesn't seem to allow the latter easily.

Fixes: effd60c878176bcaf97fa7ce2b12d04bb8ead6f7
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2126
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-id: 20240209173103.239994-1-kwolf@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
(cherry picked from commit cc29c12ec629ba68a4a6cb7d165c94cc8502815a)
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
tests/qemu-iotests/144
tests/qemu-iotests/144.out