From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: berrange@redhat.com, "Alex Bennée" <alex.bennee@linaro.org>,
"Fam Zheng" <famz@redhat.com>,
kchamart@redhat.com, eblake@redhat.com,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: [Qemu-devel] [PATCH v4 2/6] docker: Add test_fail and prep_fail
Date: Tue, 5 Sep 2017 10:56:10 +0800 [thread overview]
Message-ID: <20170905025614.579-3-famz@redhat.com> (raw)
In-Reply-To: <20170905025614.579-1-famz@redhat.com>
They both print a message and exit, but with different status code so
distinguish real test errors from env preparation failures.
Signed-off-by: Fam Zheng <famz@redhat.com>
---
tests/docker/common.rc | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/tests/docker/common.rc b/tests/docker/common.rc
index c22d825b16..63ce9a7af5 100755
--- a/tests/docker/common.rc
+++ b/tests/docker/common.rc
@@ -35,3 +35,15 @@ build_qemu()
echo $config_opts
$QEMU_SRC/configure $config_opts && make $MAKEFLAGS
}
+
+test_fail()
+{
+ echo "$@"
+ exit 1
+}
+
+prep_fail()
+{
+ echo "$@"
+ exit 2
+}
--
2.13.5
next prev parent reply other threads:[~2017-09-05 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 2:56 [Qemu-devel] [PATCH v4 0/6] docker: Add test-block Fam Zheng
2017-09-05 2:56 ` [Qemu-devel] [PATCH v4 1/6] docker: Fix return code of build_qemu() Fam Zheng
2017-09-05 2:56 ` Fam Zheng [this message]
2017-09-05 2:56 ` [Qemu-devel] [PATCH v4 3/6] docker: Use unconfined security profile Fam Zheng
2017-09-05 2:56 ` [Qemu-devel] [PATCH v4 4/6] docker: Add nettle-devel to fedora image Fam Zheng
2017-09-05 2:56 ` [Qemu-devel] [PATCH v4 5/6] docker: Add test-block Fam Zheng
2017-09-05 2:56 ` [Qemu-devel] [PATCH v4 6/6] docker: Drop 'set -e' from run script Fam Zheng
2017-09-05 9:17 ` [Qemu-devel] [PATCH v4 0/6] docker: Add test-block Stefan Hajnoczi
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=20170905025614.579-3-famz@redhat.com \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=kchamart@redhat.com \
--cc=qemu-devel@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).