qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-stable@nongnu.org,
	jack.schwartz@oracle.com, anatol.pomozov@gmail.com,
	ppandit@redhat.com
Subject: [Qemu-devel] [PATCH 3/5] tests/multiboot: Test exit code for every qemu run
Date: Wed, 14 Mar 2018 18:32:11 +0100	[thread overview]
Message-ID: <20180314173213.18563-4-kwolf@redhat.com> (raw)
In-Reply-To: <20180314173213.18563-1-kwolf@redhat.com>

Testing the exit code only once after a whole group of tests has
completed is not enough, it catches errors only in the very last qemu
invocation. We need to have the check after each qemu run.

The logging and diff with the reference output is still done once per
group to keep things more managable. This is not a problem because the
log file accumulates the output of all runs.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
 tests/multiboot/run_test.sh | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/tests/multiboot/run_test.sh b/tests/multiboot/run_test.sh
index 0278148b43..bc9c3670af 100755
--- a/tests/multiboot/run_test.sh
+++ b/tests/multiboot/run_test.sh
@@ -38,6 +38,17 @@ run_qemu() {
     ret=$?
 
     cat test.out >> test.log
+
+    debugexit=$((ret & 0x1))
+    ret=$((ret >> 1))
+
+    if [ $debugexit != 1 ]; then
+        printf %b "\e[31m ?? \e[0m $kernel $* (no debugexit used, exit code $ret)\n"
+        pass=0
+    elif [ $ret != 0 ]; then
+        printf %b "\e[31mFAIL\e[0m $kernel $* (exit code $ret)\n"
+        pass=0
+    fi
 }
 
 mmap() {
@@ -61,19 +72,8 @@ make all
 for t in mmap modules; do
 
     echo > test.log
-    $t
-
-    debugexit=$((ret & 0x1))
-    ret=$((ret >> 1))
     pass=1
-
-    if [ $debugexit != 1 ]; then
-        printf %b "\e[31m ?? \e[0m $t (no debugexit used, exit code $ret)\n"
-        pass=0
-    elif [ $ret != 0 ]; then
-        printf %b "\e[31mFAIL\e[0m $t (exit code $ret)\n"
-        pass=0
-    fi
+    $t
 
     if ! diff $t.out test.log > /dev/null 2>&1; then
         printf %b "\e[31mFAIL\e[0m $t (output difference)\n"
-- 
2.13.6

  parent reply	other threads:[~2018-03-14 17:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 17:32 [Qemu-devel] [PATCH 0/5] multiboot: Fix buffer overflow on invalid kernels Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 1/5] multiboot: Reject kernels exceeding the address space Kevin Wolf
2018-03-15  5:19   ` Jack Schwartz
2018-03-15 15:54     ` Kevin Wolf
2018-03-15 16:55       ` Jack Schwartz
2018-03-15 17:18         ` Kevin Wolf
2018-03-15 19:50           ` Jack Schwartz
2018-03-14 17:32 ` [Qemu-devel] [PATCH 2/5] multiboot: Check validity of mh_header_addr Kevin Wolf
2018-03-14 17:32 ` Kevin Wolf [this message]
2018-03-14 17:32 ` [Qemu-devel] [PATCH 4/5] tests/multiboot: Add tests for the a.out kludge Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 5/5] tests/multiboot: Add .gitignore Kevin Wolf
2018-03-14 17:43   ` Eric Blake
2018-03-14 17:50     ` Eric Blake
2018-03-15  5:19 ` [Qemu-devel] [PATCH 0/5] multiboot: Fix buffer overflow on invalid kernels Jack Schwartz

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=20180314173213.18563-4-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=anatol.pomozov@gmail.com \
    --cc=jack.schwartz@oracle.com \
    --cc=ppandit@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).