From: Lei Yang <Lei.Yang@windriver.com>
To: <lei.yang@windriver.com>, <shuahkh@osg.samsung.com>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH] selftests: add "PASS" status in log for mqueue
Date: Sun, 5 Nov 2017 17:22:00 +0800 [thread overview]
Message-ID: <1509873720-618-1-git-send-email-Lei.Yang@windriver.com> (raw)
It prints 'FAIL' status when test failed, but not print
'PASS' when test passed.
Signed-off-by: Lei Yang <Lei.Yang@windriver.com>
---
tools/testing/selftests/mqueue/Makefile | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/testing/selftests/mqueue/Makefile b/tools/testing/selftests/mqueue/Makefile
index 0f5e347..437b048 100644
--- a/tools/testing/selftests/mqueue/Makefile
+++ b/tools/testing/selftests/mqueue/Makefile
@@ -5,12 +5,12 @@ TEST_GEN_PROGS := mq_open_tests mq_perf_tests
include ../lib.mk
override define RUN_TESTS
- $(OUTPUT)/mq_open_tests /test1 || echo "selftests: mq_open_tests [FAIL]"
- $(OUTPUT)//mq_perf_tests || echo "selftests: mq_perf_tests [FAIL]"
+ $(OUTPUT)/mq_open_tests /test1 && echo "selftests: mq_open_tests [PASS]" || echo "selftests: mq_open_tests [FAIL]"
+ $(OUTPUT)/mq_perf_tests && echo "selftests: mq_perf_tests [PASS]" || echo "selftests: mq_perf_tests [FAIL]"
endef
override define EMIT_TESTS
- echo "./mq_open_tests /test1 || echo \"selftests: mq_open_tests [FAIL]\""
- echo "./mq_perf_tests || echo \"selftests: mq_perf_tests [FAIL]\""
+ echo "./mq_open_tests /test1 && echo \"selftests: mq_open_tests [PASS]\" || echo \"selftests: mq_open_tests [FAIL]\""
+ echo "./mq_perf_tests && echo \"selftests: mq_perf_tests [PASS]\" || echo \"selftests: mq_perf_tests [FAIL]\""
endef
--
1.9.1
next reply other threads:[~2017-11-05 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 9:22 Lei Yang [this message]
2017-11-06 23:37 ` Shuah Khan
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=1509873720-618-1-git-send-email-Lei.Yang@windriver.com \
--to=lei.yang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuahkh@osg.samsung.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
all inboxes | Powered by JetHome®