a98b1a1fef
We generally include relevant HMP input in .out files, by virtue of
the fact that HMP echoes its input. But QMP does not, so we have to
explicitly inject it in the output stream (appropriately filtered to
keep the tests passing), in order to make it easier to read .out files
to see what behavior is being tested (especially true where the output
file is a sequence of {'return': {}}).
Suggested-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20191114213415.23499-4-eblake@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
16 lines
469 B
Plaintext
16 lines
469 B
Plaintext
QA output created by 200
|
|
Formatting 'TEST_DIR/backing.img', fmt=IMGFMT size=536870912
|
|
Formatting 'TEST_DIR/test.img', fmt=IMGFMT size=536870912 backing_file=TEST_DIR/backing.img backing_fmt=IMGFMT
|
|
wrote 314572800/314572800 bytes at offset 512
|
|
300 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
=== Starting QEMU VM ===
|
|
|
|
{ 'execute': 'qmp_capabilities' }
|
|
{"return": {}}
|
|
|
|
=== Sending stream/cancel, checking for SIGSEGV only ===
|
|
|
|
500 iterations performed
|
|
*** done
|