All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: linux-parisc@vger.kernel.org,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	John David Anglin <dave.anglin@bell.net>
Cc: Paul Moore <paul@paul-moore.com>,
	libseccomp@googlegroups.com, Mike Frysinger <vapier@gentoo.org>
Subject: [PATCH] libseccomp/tests: Report if test was skipped because of missing valgrind
Date: Fri, 15 Apr 2016 17:09:41 +0200	[thread overview]
Message-ID: <20160415150941.GA11180@ls3530.dhcp.wdf.sap.corp> (raw)
In-Reply-To: <571103AD.20500@gmx.de>

Print a message if a regression test was skipped just because valgrind isn't
installed.

This additional info is useful for architectures (e.g. parisc) which aren't as
fast as x86_64. On parisc it seemed that the whole testcase was hanging, now
people know what's actually happening.

Signed-off-by: Helge Deller <deller@gmx.de>

diff --git a/tests/regression b/tests/regression
index 53d26b2..5949459 100755
--- a/tests/regression
+++ b/tests/regression
@@ -772,6 +773,7 @@ function run_test() {
 		if check_deps valgrind; then
 			run_test_bpf_valgrind "$testnumstr" "$3"
 		else
+			print_result $testnumstr "SKIPPED" "(valgrind not installed)"
 			stats_skipped=$(($stats_skipped+1))
 		fi
 	elif [[ "$4" == "live" ]]; then

-- 
You received this message because you are subscribed to the Google Groups "libseccomp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to libseccomp+unsubscribe@googlegroups.com.
To post to this group, send email to libseccomp@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2016-04-15 15:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160213200731.GA18161@ls3530.box>
     [not found] ` <3673666.V2ZqGazvLY@sifl>
     [not found]   ` <56C24911.8000200@gmx.de>
     [not found]     ` <1907254.cBdVSxntFv@sifl>
2016-04-09  7:05       ` [PATCH] libseccomp: Add parisc architecture support (v2) Helge Deller
2016-04-14 23:14         ` Paul Moore
2016-04-15 15:07           ` Helge Deller
2016-04-15 15:09             ` Helge Deller [this message]
2016-04-18 22:37               ` [PATCH] libseccomp/tests: Report if test was skipped because of missing valgrind Paul Moore
2016-04-15 15:11             ` [PATCH] libseccomp: Add parisc architecture support (v3) Helge Deller
2016-04-30 20:51               ` Helge Deller
2016-05-24 19:09                 ` Paul Moore
2016-05-25 14:53                   ` Re: [PATCH] libseccomp: Add parisc architecture support (v4) Helge Deller
2016-05-25 19:49                     ` Paul Moore

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=20160415150941.GA11180@ls3530.dhcp.wdf.sap.corp \
    --to=deller@gmx.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=libseccomp@googlegroups.com \
    --cc=linux-parisc@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=vapier@gentoo.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.