[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PULL 2/4] iotests: Fix "no qualified output" error path
From: |
Kevin Wolf |
Subject: |
[PULL 2/4] iotests: Fix "no qualified output" error path |
Date: |
Mon, 18 Nov 2019 18:02:54 +0100 |
The variable for error messages to be displayed is $results, not
$reason. Fix 'check' to print the "no qualified output" error message
again instead of having a failure without any message telling the user
why it failed.
Signed-off-by: Kevin Wolf <address@hidden>
Reviewed-by: Max Reitz <address@hidden>
---
tests/qemu-iotests/check | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/check b/tests/qemu-iotests/check
index 71fe38834e..90970b0549 100755
--- a/tests/qemu-iotests/check
+++ b/tests/qemu-iotests/check
@@ -887,7 +887,7 @@ do
if [ ! -f "$reference" ]
then
status="fail"
- reason="no qualified output"
+ results="no qualified output"
err=true
else
if diff -w "$reference" $tmp.out >/dev/null 2>&1
--
2.20.1
- [PULL 0/4] Block layer patches for 4.2.0-rc2, Kevin Wolf, 2019/11/18
- [PULL 2/4] iotests: Fix "no qualified output" error path,
Kevin Wolf <=
- [PULL 1/4] qemu-iotests/iotests.py: improve assert_qmp message, Kevin Wolf, 2019/11/18
- [PULL 3/4] block: Remove 'backing': null from bs->{explicit_, }options, Kevin Wolf, 2019/11/18
- [PULL 4/4] iotests: Test multiple blockdev-snapshot calls, Kevin Wolf, 2019/11/18
- Re: [PULL 0/4] Block layer patches for 4.2.0-rc2, Peter Maydell, 2019/11/18