From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Riccardo Mancini <rickyman7@gmail.com>,
Sohaib Mohamed <sohaib.amhmd@gmail.com>,
Carsten Haitzler <carsten.haitzler@arm.com>,
Marco Elver <elver@google.com>,
John Garry <john.garry@huawei.com>,
Michael Petlan <mpetlan@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Stephane Eranian <eranian@google.com>, Ian Rogers <irogers@google.com>
Subject: [PATCH 0/7] Make more tests skip rather than fail
Date: Thu, 12 May 2022 21:05:12 -0700 [thread overview]
Message-ID: <20220513040519.1499333-1-irogers@google.com> (raw)
A long standing niggle has been that tests that cannot pass are marked
as failing rather than skip. John Garry mentioned a similar concern
in [1]. These changes fix this behavior so that as root, or not, at
least the first 10 tests are passing or skipping.
[1] https://lore.kernel.org/lkml/d32376b5-5538-ff00-6620-e74ad4b4abf2@huawei.com/
Ian Rogers (7):
perf test: Skip reason for suites with 1 test
perf test: Use skip in vmlinux kallsyms
perf test: Use skip in openat syscall
perf test: Basic mmap use skip
perf test: Parse events tidy terms_test
perf test: Parse events tidy evlist_test
perf test: Parse events break apart tests
tools/perf/tests/builtin-test.c | 6 +-
tools/perf/tests/mmap-basic.c | 22 +-
tools/perf/tests/openat-syscall-all-cpus.c | 23 +-
tools/perf/tests/openat-syscall.c | 20 +-
tools/perf/tests/parse-events.c | 492 +++++++++++----------
tools/perf/tests/vmlinux-kallsyms.c | 12 +-
6 files changed, 329 insertions(+), 246 deletions(-)
--
2.36.0.550.gb090851708-goog
next reply other threads:[~2022-05-13 4:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 4:05 Ian Rogers [this message]
2022-05-13 4:05 ` [PATCH 1/7] perf test: Skip reason for suites with 1 test Ian Rogers
2022-05-13 15:29 ` John Garry
2022-05-13 15:42 ` Ian Rogers
2022-05-13 16:26 ` John Garry
2022-05-13 16:34 ` Ian Rogers
2022-05-13 16:46 ` John Garry
2022-05-17 3:53 ` Namhyung Kim
2022-05-13 4:05 ` [PATCH 2/7] perf test: Use skip in vmlinux kallsyms Ian Rogers
2022-05-13 17:01 ` John Garry
2022-05-13 17:05 ` Ian Rogers
2022-05-17 3:21 ` Namhyung Kim
2022-05-18 3:37 ` Ian Rogers
2022-05-13 4:05 ` [PATCH 3/7] perf test: Use skip in openat syscall Ian Rogers
2022-05-13 4:05 ` [PATCH 4/7] perf test: Basic mmap use skip Ian Rogers
2022-05-17 3:42 ` Namhyung Kim
2022-05-18 3:48 ` Ian Rogers
2022-05-13 4:05 ` [PATCH 5/7] perf test: Parse events tidy terms_test Ian Rogers
2022-05-13 4:05 ` [PATCH 6/7] perf test: Parse events tidy evlist_test Ian Rogers
2022-05-13 4:05 ` [PATCH 7/7] perf test: Parse events break apart tests Ian Rogers
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=20220513040519.1499333-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=carsten.haitzler@arm.com \
--cc=elver@google.com \
--cc=eranian@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rickyman7@gmail.com \
--cc=sohaib.amhmd@gmail.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).