From: Thomas Huth <thuth@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Janosch Frank <frankja@linux.ibm.com>
Subject: [kvm-unit-tests PULL 02/11] Use same test names in the default and the TAP13 output format
Date: Mon, 28 Sep 2020 19:49:49 +0200 [thread overview]
Message-ID: <20200928174958.26690-3-thuth@redhat.com> (raw)
In-Reply-To: <20200928174958.26690-1-thuth@redhat.com>
From: Marc Hartmayer <mhartmay@linux.ibm.com>
Use the same test names in the TAP13 output as in the default output
format. This makes the output more consistent. To achieve this, we
need to pass the test name as an argument to the function
`process_test_output`.
Before this change:
$ ./run_tests.sh
PASS selftest-setup (14 tests)
...
vs.
$ ./run_tests.sh -t
TAP version 13
ok 1 - selftest: true
ok 2 - selftest: argc == 3
...
After this change:
$ ./run_tests.sh
PASS selftest-setup (14 tests)
...
vs.
$ ./run_tests.sh -t
TAP version 13
ok 1 - selftest-setup: selftest: true
ok 2 - selftest-setup: selftest: argc == 3
...
While at it, introduce a local variable `kernel` in
`RUNTIME_log_stdout` since this makes the function easier to read.
Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com>
Message-Id: <20200825102036.17232-3-mhartmay@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
run_tests.sh | 15 +++++++++------
scripts/runtime.bash | 6 +++---
2 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/run_tests.sh b/run_tests.sh
index fc4b3c2..d7cad9b 100755
--- a/run_tests.sh
+++ b/run_tests.sh
@@ -88,18 +88,19 @@ if [[ $tap_output == "no" ]]; then
postprocess_suite_output() { cat; }
else
process_test_output() {
+ local testname="$1"
CR=$'\r'
while read -r line; do
line="${line%$CR}"
case "${line:0:4}" in
PASS)
- echo "ok TEST_NUMBER - ${line#??????}" >&3
+ echo "ok TEST_NUMBER - ${testname}: ${line#??????}" >&3
;;
FAIL)
- echo "not ok TEST_NUMBER - ${line#??????}" >&3
+ echo "not ok TEST_NUMBER - ${testname}: ${line#??????}" >&3
;;
SKIP)
- echo "ok TEST_NUMBER - ${line#??????} # skip" >&3
+ echo "ok TEST_NUMBER - ${testname}: ${line#??????} # skip" >&3
;;
*)
;;
@@ -121,12 +122,14 @@ else
}
fi
-RUNTIME_log_stderr () { process_test_output; }
+RUNTIME_log_stderr () { process_test_output "$1"; }
RUNTIME_log_stdout () {
+ local testname="$1"
if [ "$PRETTY_PRINT_STACKS" = "yes" ]; then
- ./scripts/pretty_print_stacks.py $1 | process_test_output
+ local kernel="$2"
+ ./scripts/pretty_print_stacks.py "$kernel" | process_test_output "$testname"
else
- process_test_output
+ process_test_output "$testname"
fi
}
diff --git a/scripts/runtime.bash b/scripts/runtime.bash
index caa4c5b..294e6b1 100644
--- a/scripts/runtime.bash
+++ b/scripts/runtime.bash
@@ -140,10 +140,10 @@ function run()
# extra_params in the config file may contain backticks that need to be
# expanded, so use eval to start qemu. Use "> >(foo)" instead of a pipe to
# preserve the exit status.
- summary=$(eval $cmdline 2> >(RUNTIME_log_stderr) \
- > >(tee >(RUNTIME_log_stdout $kernel) | extract_summary))
+ summary=$(eval $cmdline 2> >(RUNTIME_log_stderr $testname) \
+ > >(tee >(RUNTIME_log_stdout $testname $kernel) | extract_summary))
ret=$?
- [ "$STANDALONE" != "yes" ] && echo > >(RUNTIME_log_stdout $kernel)
+ [ "$STANDALONE" != "yes" ] && echo > >(RUNTIME_log_stdout $testname $kernel)
if [ $ret -eq 0 ]; then
print_result "PASS" $testname "$summary"
--
2.18.2
next prev parent reply other threads:[~2020-09-28 17:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 17:49 [kvm-unit-tests PULL 00/11] s390x and generic script updates Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 01/11] runtime.bash: remove outdated comment Thomas Huth
2020-09-28 17:49 ` Thomas Huth [this message]
2020-09-28 17:49 ` [kvm-unit-tests PULL 03/11] configure: Add a check for the bash version Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 04/11] travis.yml: Update from Bionic to Focal Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 05/11] travis.yml: Update the list of s390x tests Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 06/11] common.bash: run `cmd` only if a test case was found Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 07/11] scripts: add support for architecture dependent functions Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 08/11] run_tests/mkstandalone: add arch_cmd hook Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 09/11] s390x: add Protected VM support Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 10/11] s390x/selftest: Fix constraint of inline assembly Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 11/11] scripts/arch-run: use ncat rather than nc Thomas Huth
2020-09-29 8:38 ` [kvm-unit-tests PULL 00/11] s390x and generic script updates Paolo Bonzini
2020-09-29 8:47 ` Thomas Huth
2020-09-29 8:49 ` Janosch Frank
2020-09-29 8:58 ` Thomas Huth
2020-09-29 9:06 ` Paolo Bonzini
2020-10-01 9:21 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200928174958.26690-3-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox