4e2f441878
During 'qemu-img create ... 2>&1', if --quiet is not in force, we can end up with buffered I/O in stdout that was produced before failure, but which appears in output after failure. This is confusing; the fix is to flush stdout prior to attempting anything that might produce an error message. Several iotests demonstrate the resulting ordering change now that the merged outputs now reflect chronology. (An even better fix would be to avoid printf from within block.c altogether, but that's much more invasive...) Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <20200706203954.341758-2-eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
12 lines
530 B
Plaintext
12 lines
530 B
Plaintext
QA output created by 282
|
|
== Create non-UTF8 secret ==
|
|
== Throws an error because of invalid UTF-8 secret ==
|
|
Formatting 'vol.img', fmt=luks size=4194304 key-secret=sec0
|
|
qemu-img: vol.img: Data from secret sec0 is not valid UTF-8
|
|
== Image file should not exist after the error ==
|
|
== Create a stub image file and run qemu-img again ==
|
|
Formatting 'vol.img', fmt=luks size=4194304 key-secret=sec0
|
|
qemu-img: vol.img: Data from secret sec0 is not valid UTF-8
|
|
== Pre-existing image file should also be deleted after the error ==
|
|
*** done
|