| commit | a47295014de56e108f359ec859d5499b851f62b8 | |
| author | Peter Xu <peterx@redhat.com> | |
| Wed, 21 Oct 2020 21:27:21 +0000 (21 17:27 -0400) | ||
| committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Mon, 26 Oct 2020 16:15:04 +0000 (26 16:15 +0000) | ||
| tree | 747063a0318eee9983167e912f15332f9c0a448a | treesnapshot (tar.gz zip) |
| parent | d246ea5039fd6d5344becd0943fcbb7f8e6bbfe7 | commitdiff |
migration-test: Only hide error if !QTEST_LOG
The errors are very useful when debugging qtest failures, especially when
QTEST_LOG=1 is set. Let's allow override MigrateStart.hide_stderr when
QTEST_LOG=1 is specified, because that means the user wants to be verbose.
Not very nice to introduce the first QTEST_LOG env access in migration-test.c,
however it should be handy. Without this patch, I was hacking error_report()
when debugging such errors. Let's make things easier.
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20201021212721.440373-7-peterx@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
The errors are very useful when debugging qtest failures, especially when
QTEST_LOG=1 is set. Let's allow override MigrateStart.hide_stderr when
QTEST_LOG=1 is specified, because that means the user wants to be verbose.
Not very nice to introduce the first QTEST_LOG env access in migration-test.c,
however it should be handy. Without this patch, I was hacking error_report()
when debugging such errors. Let's make things easier.
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20201021212721.440373-7-peterx@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
| tests/qtest/migration-test.c | diffblobblamehistory |