From: KP Singh <kpsingh@kernel.org>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Florent Revest <revest@chromium.org>,
Brendan Jackman <jackmanb@chromium.org>
Subject: [PATCH bpf-next v3 0/2] BPF selftest helper script
Date: Mon, 1 Feb 2021 00:50:16 +0000 [thread overview]
Message-ID: <20210201005018.25808-1-kpsingh@kernel.org> (raw)
# v2 -> v3
- Fixes to silence verbose commands
- Fixed output buffering without being teed out
- Fixed the clobbered error code of the script
- Other fixes suggested by Andrii
# v1 -> v2
- The script now compiles the kernel by default, and the -k option
implies "keep the kernel"
- Pointer to the script in the docs.
- Some minor simplifications.
Allow developers and contributors to understand if their changes would
end up breaking the BPF CI and avoid the back and forth required for
fixing the test cases in the CI environment. The series also adds a
pointer in tools/testing/selftests/bpf/README.rst.
KP Singh (2):
bpf: Helper script for running BPF presubmit tests
bpf/selftests: Add a short note about run_in_vm.sh in README.rst
tools/testing/selftests/bpf/README.rst | 24 ++
tools/testing/selftests/bpf/run_in_vm.sh | 356 +++++++++++++++++++++++
2 files changed, 380 insertions(+)
create mode 100755 tools/testing/selftests/bpf/run_in_vm.sh
--
2.30.0.365.g02bc693789-goog
next reply other threads:[~2021-02-01 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 0:50 KP Singh [this message]
2021-02-01 0:50 ` [PATCH bpf-next v3 1/2] bpf: Helper script for running BPF presubmit tests KP Singh
2021-02-01 0:50 ` [PATCH bpf-next v3 2/2] bpf/selftests: Add a short note about run_in_vm.sh in README.rst KP Singh
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=20210201005018.25808-1-kpsingh@kernel.org \
--to=kpsingh@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jackmanb@chromium.org \
--cc=revest@chromium.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).