[subject line kept for continuity with v1, but now touches much more] Max suggested that instead of special-casing just 223 to trace QMP input as well output, that we should instead patch common.qemu to do it for all tests. That in turn found that test 173 has been broken since v3.0. Max also suggested that 223 use a for loop rather than massive code duplication, which does indeed look nicer.
Eric Blake (3): iotests: Fix 173 iotests: Include QMP input in .out files tests: More iotest 223 improvements tests/qemu-iotests/common.qemu | 9 +++ tests/qemu-iotests/085.out | 26 +++++++++ tests/qemu-iotests/094.out | 4 ++ tests/qemu-iotests/095.out | 2 + tests/qemu-iotests/109.out | 88 +++++++++++++++++++++++++++++ tests/qemu-iotests/117.out | 5 ++ tests/qemu-iotests/127.out | 4 ++ tests/qemu-iotests/140.out | 5 ++ tests/qemu-iotests/141.out | 26 +++++++++ tests/qemu-iotests/143.out | 3 + tests/qemu-iotests/144.out | 5 ++ tests/qemu-iotests/153.out | 11 ++++ tests/qemu-iotests/156.out | 11 ++++ tests/qemu-iotests/161.out | 8 +++ tests/qemu-iotests/173 | 4 +- tests/qemu-iotests/173.out | 10 +++- tests/qemu-iotests/182.out | 8 +++ tests/qemu-iotests/183.out | 11 ++++ tests/qemu-iotests/185.out | 18 ++++++ tests/qemu-iotests/191.out | 8 +++ tests/qemu-iotests/200.out | 1 + tests/qemu-iotests/223 | 16 +++++- tests/qemu-iotests/223.out | 100 +++++++++++++++++++++++++++++++++ tests/qemu-iotests/229.out | 3 + tests/qemu-iotests/249.out | 6 ++ 25 files changed, 387 insertions(+), 5 deletions(-) -- 2.21.0
