public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Richter <tmricht@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-perf-users@vger.kernel.org, acme@kernel.org,
	namhyung@kernel.org, howardchu95@gmail.com
Cc: agordeev@linux.ibm.com, gor@linux.ibm.com,
	sumanthk@linux.ibm.com, hca@linux.ibm.com, japo@linux.ibm.com,
	Thomas Richter <tmricht@linux.ibm.com>
Subject: [PATCH] perf test: Make perf trace enum augmentation tests exclusive
Date: Thu,  9 Apr 2026 10:11:54 +0200	[thread overview]
Message-ID: <20260409081154.318898-1-tmricht@linux.ibm.com> (raw)

Running both tests cases 'perf trace enum augmentation tests'
and 'perf trace BTF general tests' together causes the first test case
to fail:
 # for i in $(seq 5); do \
	./perf test 'perf trace enum augmentation tests' \
	'perf trace BTF general tests'; \
   done
 125: perf trace enum augmentation tests  : Ok
 126: perf trace BTF general tests        : FAILED!
 125: perf trace enum augmentation tests  : Ok
 126: perf trace BTF general tests        : FAILED!
 125: perf trace enum augmentation tests  : Ok
 126: perf trace BTF general tests        : FAILED!
 125: perf trace enum augmentation tests  : Ok
 126: perf trace BTF general tests        : FAILED!
 125: perf trace enum augmentation tests  : Ok
 126: perf trace BTF general tests        : FAILED!
 #

Test case perf trace enum augmentation tests' fails because  the second
test case 'perf trace BTF general tests' runs concurrently as can
be observed using a ps -ef | grep perf output list on a different
window. Both do a perf trace command concurrently.
Make test case 'perf trace enum augmentation tests' exclusive.

 # for i in $(seq 5); do \
	./perf test 'perf trace enum augmentation tests' \
	'perf trace BTF general tests'; \
   done
 125: perf trace BTF general tests        : Ok
 155: perf trace enum augmentation tests  : Ok
 125: perf trace BTF general tests        : Ok
 155: perf trace enum augmentation tests  : Ok
 125: perf trace BTF general tests        : Ok
 155: perf trace enum augmentation tests  : Ok
 125: perf trace BTF general tests        : Ok
 155: perf trace enum augmentation tests  : Ok
 125: perf trace BTF general tests        : Ok
 155: perf trace enum augmentation tests  : Ok
 #

Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
Cc: Howard Chu <howardchu95@gmail.com>
---
 tools/perf/tests/shell/trace_btf_enum.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/perf/tests/shell/trace_btf_enum.sh b/tools/perf/tests/shell/trace_btf_enum.sh
index 03e9f680a4a6..437510d46f58 100755
--- a/tools/perf/tests/shell/trace_btf_enum.sh
+++ b/tools/perf/tests/shell/trace_btf_enum.sh
@@ -1,5 +1,5 @@
 #!/bin/bash
-# perf trace enum augmentation tests
+# perf trace enum augmentation tests (exclusive)
 # SPDX-License-Identifier: GPL-2.0
 
 err=0
-- 
2.53.0


             reply	other threads:[~2026-04-09  8:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09  8:11 Thomas Richter [this message]
2026-04-09 14:22 ` [PATCH] perf test: Make perf trace enum augmentation tests exclusive Howard Chu

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=20260409081154.318898-1-tmricht@linux.ibm.com \
    --to=tmricht@linux.ibm.com \
    --cc=acme@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=howardchu95@gmail.com \
    --cc=japo@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=sumanthk@linux.ibm.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