aboutsummaryrefslogtreecommitdiff
path: root/tests/qemu-iotests/197
diff options
context:
space:
mode:
authorStefan Hajnoczi <stefanha@redhat.com>2024-01-18 09:48:22 -0500
committerMichael Tokarev <mjt@tls.msk.ru>2024-01-26 19:31:33 +0300
commit823892d19f6b79dc44ac1a885a9ceed0bd0965e7 (patch)
tree9633552c72c560b9e3a85e55cd8889e178f98007 /tests/qemu-iotests/197
parentd7a64c4517c2b59429ac7edea7c2b52e4806e135 (diff)
downloadqemu-823892d19f6b79dc44ac1a885a9ceed0bd0965e7.zip
qemu-823892d19f6b79dc44ac1a885a9ceed0bd0965e7.tar.gz
qemu-823892d19f6b79dc44ac1a885a9ceed0bd0965e7.tar.bz2
iotests: port 141 to Python for reliable QMP testing
The common.qemu bash functions allow tests to interact with the QMP monitor of a QEMU process. I spent two days trying to update 141 when the order of the test output changed, but found it would still fail occassionally because printf() and QMP events race with synchronous QMP communication. I gave up and ported 141 to the existing Python API for QMP tests. The Python API is less affected by the order in which QEMU prints output because it does not print all QMP traffic by default. The next commit changes the order in which QMP messages are received. Make 141 reliable first. Cc: Hanna Czenczek <hreitz@redhat.com> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Message-ID: <20240118144823.1497953-3-stefanha@redhat.com> Reviewed-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com> (cherry picked from commit 9ee2dd4c22a3639c5462b3fc20df60c005c3de64) Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Diffstat (limited to 'tests/qemu-iotests/197')
0 files changed, 0 insertions, 0 deletions