diff options
| author | Eric Blake <eblake@redhat.com> | 2019-11-14 15:34:12 -0600 |
|---|---|---|
| committer | Eric Blake <eblake@redhat.com> | 2019-11-18 16:01:34 -0600 |
| commit | 509e91c127390343b7688ddea0b908fa3e8b2707 (patch) | |
| tree | 841b89684a9e23b21f9c865364a0eac4154524b5 /scripts/qapi/doc.py | |
| parent | 052db8e71444d85036bee2d3e3225ba9a6d652ee (diff) | |
| download | focaccia-qemu-509e91c127390343b7688ddea0b908fa3e8b2707.tar.gz focaccia-qemu-509e91c127390343b7688ddea0b908fa3e8b2707.zip | |
iotests: Fix 173
This test has been broken since 3.0. It used TEST_IMG to influence the name of a file created during _make_test_img, but commit 655ae6bb changed things so that the wrong file name is being created, which then caused _launch_qemu to fail. In the meantime, the set of events issued for the actions of the test has increased. Why haven't we noticed the failure? Because the test rarely gets run: './check -qcow2 173' is insufficient (that defaults to using file protocol) './check -nfs 173' is insufficient (that defaults to using raw format) so the test is only run with: ./check -qcow2 -nfs 173 Note that we already have a number of other problems with -nfs: ./check -nfs (fails 18/30) ./check -qcow2 -nfs (fails 45/76 after this patch, if exports does not permit 'insecure') and it's not on my priority list to fix those. Rather, I found this because of my next patch's work on tests using _send_qemu_cmd. Fixes: 655ae6b Signed-off-by: Eric Blake <eblake@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com> Message-Id: <20191114213415.23499-2-eblake@redhat.com>
Diffstat (limited to 'scripts/qapi/doc.py')
0 files changed, 0 insertions, 0 deletions