| commit | a19052496709d0999d777f0cb1fbd532958196c6 | |
| author | John Snow <jsnow@redhat.com> | |
| Mon, 18 Apr 2022 21:14:54 +0000 (18 17:14 -0400) | ||
| committer | Hanna Reitz <hreitz@redhat.com> | |
| Mon, 25 Apr 2022 12:30:03 +0000 (25 14:30 +0200) | ||
| tree | 746013e638bde0ee8d8c56bf1e3b070f051df4ac | treesnapshot (tar.gz zip) |
| parent | 093a13acbf6be15de01cbf4afc27fb4193fd49ee | commitdiff |
iotests/163: Fix broken qemu-io invocation
The 'read' commands to qemu-io were malformed, and this invocation only
worked by coincidence because the error messages were identical. Oops.
There's no point in checking the patterning of the reference image, so
just check the empty image by itself instead.
(Note: as of this commit, nothing actually enforces that this command
completes successfully, but a forthcoming commit in this series will
enforce that qemu_io() must have a zero status code.)
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Message-Id: <20220418211504.943969-3-jsnow@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
The 'read' commands to qemu-io were malformed, and this invocation only
worked by coincidence because the error messages were identical. Oops.
There's no point in checking the patterning of the reference image, so
just check the empty image by itself instead.
(Note: as of this commit, nothing actually enforces that this command
completes successfully, but a forthcoming commit in this series will
enforce that qemu_io() must have a zero status code.)
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Message-Id: <20220418211504.943969-3-jsnow@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
| tests/qemu-iotests/163 | diffblobblamehistory |