linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: tglx@linutronix.de, mhiramat@kernel.org, namhyung@kernel.org,
	vedang.patel@intel.com, bigeasy@linutronix.de,
	joel@joelfernandes.org, mathieu.desnoyers@efficios.com,
	julia@ni.com, linux-kernel@vger.kernel.org,
	linux-rt-users@vger.kernel.org
Subject: [PATCH v10 15/15] tracing: Add hist trigger action 'expected fail' test case
Date: Fri, 21 Dec 2018 10:29:14 -0600	[thread overview]
Message-ID: <b4a712716b1b94d487cf9811475a3b8702ed4cb5.1545408962.git.tom.zanussi@linux.intel.com> (raw)
In-Reply-To: <cover.1545408962.git.tom.zanussi@linux.intel.com>
In-Reply-To: <cover.1545408962.git.tom.zanussi@linux.intel.com>

From: Tom Zanussi <tom.zanussi@linux.intel.com>

Add a test case verifying that basic action combinations fail as
expected.

Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
---
 .../inter-event/trigger-action-hist-xfail.tc       | 30 ++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-action-hist-xfail.tc

diff --git a/tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-action-hist-xfail.tc b/tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-action-hist-xfail.tc
new file mode 100644
index 000000000000..1221240f8cf6
--- /dev/null
+++ b/tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-action-hist-xfail.tc
@@ -0,0 +1,30 @@
+#!/bin/sh
+# SPDX-License-Identifier: GPL-2.0
+# description: event trigger - test inter-event histogram trigger expected fail actions
+
+fail() { #msg
+    echo $1
+    exit_fail
+}
+
+if [ ! -f set_event ]; then
+    echo "event tracing is not supported"
+    exit_unsupported
+fi
+
+if [ ! -f snapshot ]; then
+    echo "snapshot is not supported"
+    exit_unsupported
+fi
+
+grep -q "snapshot()" README || exit_unsupported # version issue
+
+echo "Test expected snapshot action failure"
+
+echo 'hist:keys=comm:onmatch(sched.sched_wakeup).snapshot()' >> /sys/kernel/debug/tracing/events/sched/sched_waking/trigger && exit_fail
+
+echo "Test expected save action failure"
+
+echo 'hist:keys=comm:onmatch(sched.sched_wakeup).save(comm,prio)' >> /sys/kernel/debug/tracing/events/sched/sched_waking/trigger && exit_fail
+
+exit_xfail
-- 
2.14.1


      parent reply	other threads:[~2018-12-21 16:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 16:28 [PATCH v10 00/15] tracing: Hist trigger snapshot and onchange additions Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 01/15] tracing: Refactor hist trigger action code Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 02/15] tracing: Make hist trigger Documentation better reflect actions/handlers Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 03/15] tracing: Split up onmatch action data Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 04/15] tracing: Generalize hist trigger onmax and save action Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 05/15] tracing: Add conditional snapshot Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 06/15] tracing: Add hist trigger snapshot() action Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 07/15] tracing: Add hist trigger snapshot() action Documentation Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 08/15] tracing: Add hist trigger onchange() handler Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 09/15] tracing: Add hist trigger onchange() handler Documentation Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 10/15] tracing: Add alternative synthetic event trace action syntax Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 11/15] tracing: Add SPDX license GPL-2.0 license identifier to inter-event testcases Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 12/15] tracing: Add hist trigger snapshot() action test case Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 13/15] tracing: Add hist trigger onchange() handler " Tom Zanussi
2018-12-21 16:29 ` [PATCH v10 14/15] tracing: Add alternative synthetic event trace action " Tom Zanussi
2018-12-21 16:29 ` Tom Zanussi [this message]

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=b4a712716b1b94d487cf9811475a3b8702ed4cb5.1545408962.git.tom.zanussi@linux.intel.com \
    --to=zanussi@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=joel@joelfernandes.org \
    --cc=julia@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=vedang.patel@intel.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;
as well as URLs for NNTP newsgroup(s).