diff options
| author | John Snow <jsnow@redhat.com> | 2021-11-18 15:46:19 -0500 |
|---|---|---|
| committer | John Snow <jsnow@redhat.com> | 2021-11-22 18:41:21 -0500 |
| commit | 206439cd8937a3dc556537074d5d37e5d74eb0d0 (patch) | |
| tree | 683814868f15dd7d29f89c7853d9e71d3a8694da /include/qemu/progress_meter.h | |
| parent | 1611e6cf4e7163f6102b37010a8b7e7120f468b5 (diff) | |
| download | qemu-206439cd8937a3dc556537074d5d37e5d74eb0d0.zip qemu-206439cd8937a3dc556537074d5d37e5d74eb0d0.tar.gz qemu-206439cd8937a3dc556537074d5d37e5d74eb0d0.tar.bz2 | |
scripts/device-crash-test: Use a QMP timeout
Despite all the previous fixes, it's still possible for
device-crash-test to wedge itself in the case that QEMU terminates *so
quickly* that it doesn't even begin a connection attempt to our QMP
client. Python will just joyfully wait ad infinitum for a connection
that will now never arrive.
The real fix is to use asyncio to simultaneously poll both the health of
the launched process AND the connection attempt. That's quite a bit more
invasive than just setting a connection timeout, though.
Do the very simplest thing for now.
Signed-off-by: John Snow <jsnow@redhat.com>
Message-id: 20211118204620.1897674-7-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
Diffstat (limited to 'include/qemu/progress_meter.h')
0 files changed, 0 insertions, 0 deletions