| commit | 491e5e85ef7f10946762b3827eaa62635593fced | |
| author | Daniel P. Berrange <berrange@redhat.com> | |
| Mon, 21 Mar 2016 14:11:44 +0000 (21 14:11 +0000) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Wed, 30 Mar 2016 09:59:32 +0000 (30 11:59 +0200) | ||
| tree | 83d9c5dbd1492ce8b3252ac8c8d2ff19e220e0a4 | treesnapshot (tar.gz zip) |
| parent | 4ef130fca87b7a8c77e1af9ca967f28b683811d7 | commitdiff |
tests: redirect stderr to stdout for iotests
The python I/O tests helper for running qemu-img/qemu-io
setup stdout to be captured to a pipe, but left stderr
untouched. As a result, if something failed in qemu-img/
qemu-io, data written to stderr would get output directly
and not line up with data on the test stdout due to
buffering. If we explicitly redirect stderr to the same
pipe as stdout, things are much clearer when they go
wrong.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
The python I/O tests helper for running qemu-img/qemu-io
setup stdout to be captured to a pipe, but left stderr
untouched. As a result, if something failed in qemu-img/
qemu-io, data written to stderr would get output directly
and not line up with data on the test stdout due to
buffering. If we explicitly redirect stderr to the same
pipe as stdout, things are much clearer when they go
wrong.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| tests/qemu-iotests/iotests.py | diffblobblamehistory |