From: dyoung@redhat.com
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: Dave Young <dyoung@redhat.com>
Subject: [patch 7/8] kcmp selftests: print fail status instead of cause make error
Date: Sat, 24 Nov 2012 16:29:25 +0800 [thread overview]
Message-ID: <20121124083140.241502487@redhat.com> (raw)
In-Reply-To: 20121124082918.671430919@redhat.com
[-- Attachment #1: fix-kcmp-2.patch --]
[-- Type: text/plain, Size: 579 bytes --]
In case kcmp_test exit non zero value it will cause make error.
Better way is just print the test failure status.
Signed-off-by: Dave Young <dyoung@redhat.com>
---
tools/testing/selftests/kcmp/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.orig/tools/testing/selftests/kcmp/Makefile 2012-11-23 23:10:18.000000000 +0800
+++ linux-2.6/tools/testing/selftests/kcmp/Makefile 2012-11-23 23:11:52.474414896 +0800
@@ -22,7 +22,7 @@ else
endif
run_tests: all
- ./kcmp_test
+ @./kcmp_test || echo "kcmp_test: [FAIL]"
clean:
rm -fr ./run_test
next prev parent reply other threads:[~2012-11-24 8:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 8:29 [patch 0/8] several selftests fixes dyoung
2012-11-24 8:29 ` [patch 1/8] vm selftests: print failure status instead of cause make error dyoung
2012-11-24 8:29 ` [patch 2/8] mqueue " dyoung
2012-11-24 9:45 ` Pekka Enberg
2012-11-24 8:29 ` [patch 3/8] cpu-hotplug " dyoung
2012-11-24 9:43 ` Pekka Enberg
2012-11-24 8:29 ` [patch 4/8] mem-hotplug " dyoung
2012-11-24 9:42 ` Pekka Enberg
2012-11-24 8:29 ` [patch 5/8] kcmp selftests: make run_tests fix dyoung
2012-11-24 8:29 ` [patch 6/8] kcmp selftests: build fix dyoung
2012-11-24 9:41 ` Pekka Enberg
2012-11-25 3:02 ` Dave Young
2012-11-24 8:29 ` dyoung [this message]
2012-11-24 9:45 ` [patch 7/8] kcmp selftests: print fail status instead of cause make error Pekka Enberg
2012-11-24 8:29 ` [patch 8/8] breakpoint selftests: print failure " dyoung
2012-11-24 9:45 ` Pekka Enberg
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=20121124083140.241502487@redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.