From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Cc: "Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: [PATCH 0/4] trace-cmd: Make unit tests for trace-cmd
Date: Thu, 16 Jun 2022 11:29:57 -0400 [thread overview]
Message-ID: <20220616153001.649858-1-rostedt@goodmis.org> (raw)
From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
The current unit tests in the trace-cmd repo are really for libtracefs. As
libtracefs has moved to its own repo and has its own unit tests, the
trace-cmd tests here are redundant.
Remove the libtracefs unit tests and replace them with tests that are
specific for trace-cmd.
Currently there are only two tests added. A simple record and report, and a
test of converting from v7 to v6 file format. But this adds infrastructure
that should make it easier to add new tests.
Steven Rostedt (Google) (4):
trace-cmd utests: Remove libtracefs tests
trace-cmd utest: Rename tracefs-utest.c to tracecmd-utest.c
trace-cmd test: Add simple record/report test
trace-cmd test: Add test to check conversion from 7 to 6
Makefile | 2 +-
utest/Makefile | 2 +-
utest/trace-utest.c | 23 +-
utest/trace-utest.h | 7 +-
utest/tracecmd-utest.c | 295 +++++++++++++++++++
utest/tracefs-utest.c | 630 -----------------------------------------
6 files changed, 319 insertions(+), 640 deletions(-)
create mode 100644 utest/tracecmd-utest.c
delete mode 100644 utest/tracefs-utest.c
--
2.35.1
next reply other threads:[~2022-06-16 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 15:29 Steven Rostedt [this message]
2022-06-16 15:29 ` [PATCH 1/4] trace-cmd utests: Remove libtracefs tests Steven Rostedt
2022-06-16 15:29 ` [PATCH 2/4] trace-cmd utest: Rename tracefs-utest.c to tracecmd-utest.c Steven Rostedt
2022-06-16 15:30 ` [PATCH 3/4] trace-cmd test: Add simple record/report test Steven Rostedt
2022-06-16 15:30 ` [PATCH 4/4] trace-cmd test: Add test to check conversion from 7 to 6 Steven Rostedt
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=20220616153001.649858-1-rostedt@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@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 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).