From: Stanislav Fomichev <sdf@google.com>
To: netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: davem@davemloft.net, ast@kernel.org, daniel@iogearbox.net,
Stanislav Fomichev <sdf@google.com>,
Andrii Nakryiko <andriin@fb.com>
Subject: [PATCH bpf-next v3 0/4] selftests/bpf: test_progs: misc fixes
Date: Wed, 21 Aug 2019 16:44:23 -0700 [thread overview]
Message-ID: <20190821234427.179886-1-sdf@google.com> (raw)
* add test__skip to indicate skipped tests
* remove global success/error counts (use environment)
* remove asserts from the tests
* remove unused ret from send_signal test
v3:
* QCHECK -> CHECK_FAIL (Daniel Borkmann)
v2:
* drop patch that changes output to keep consistent with test_verifier
(Alexei Starovoitov)
* QCHECK instead of test__fail (Andrii Nakryiko)
* test__skip count number of subtests (Andrii Nakryiko)
Cc: Andrii Nakryiko <andriin@fb.com>
Stanislav Fomichev (4):
selftests/bpf: test_progs: test__skip
selftests/bpf: test_progs: remove global fail/success counts
selftests/bpf: test_progs: remove asserts from subtests
selftests/bpf: test_progs: remove unused ret
.../selftests/bpf/prog_tests/bpf_obj_id.c | 20 +++++----
.../bpf/prog_tests/bpf_verif_scale.c | 9 +---
.../selftests/bpf/prog_tests/flow_dissector.c | 4 +-
.../bpf/prog_tests/get_stack_raw_tp.c | 3 --
.../selftests/bpf/prog_tests/global_data.c | 20 +++------
.../selftests/bpf/prog_tests/l4lb_all.c | 9 ++--
.../selftests/bpf/prog_tests/map_lock.c | 38 ++++++++--------
.../selftests/bpf/prog_tests/pkt_access.c | 4 +-
.../selftests/bpf/prog_tests/pkt_md_access.c | 4 +-
.../bpf/prog_tests/queue_stack_map.c | 8 +---
.../bpf/prog_tests/reference_tracking.c | 4 +-
.../selftests/bpf/prog_tests/send_signal.c | 43 +++++++++----------
.../selftests/bpf/prog_tests/spinlock.c | 16 +++----
.../bpf/prog_tests/stacktrace_build_id.c | 7 +--
.../bpf/prog_tests/stacktrace_build_id_nmi.c | 7 +--
.../selftests/bpf/prog_tests/stacktrace_map.c | 17 +++-----
.../bpf/prog_tests/stacktrace_map_raw_tp.c | 9 ++--
.../bpf/prog_tests/task_fd_query_rawtp.c | 3 --
.../bpf/prog_tests/task_fd_query_tp.c | 5 ---
.../selftests/bpf/prog_tests/tcp_estats.c | 4 +-
tools/testing/selftests/bpf/prog_tests/xdp.c | 4 +-
.../bpf/prog_tests/xdp_adjust_tail.c | 4 +-
.../selftests/bpf/prog_tests/xdp_noinline.c | 8 ++--
tools/testing/selftests/bpf/test_progs.c | 41 ++++++++++++------
tools/testing/selftests/bpf/test_progs.h | 19 +++++---
25 files changed, 138 insertions(+), 172 deletions(-)
--
2.23.0.187.g17f5b7556c-goog
next reply other threads:[~2019-08-21 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 23:44 Stanislav Fomichev [this message]
2019-08-21 23:44 ` [PATCH bpf-next v3 1/4] selftests/bpf: test_progs: test__skip Stanislav Fomichev
2019-08-21 23:44 ` [PATCH bpf-next v3 2/4] selftests/bpf: test_progs: remove global fail/success counts Stanislav Fomichev
2019-08-21 23:44 ` [PATCH bpf-next v3 3/4] selftests/bpf: test_progs: remove asserts from subtests Stanislav Fomichev
2019-08-21 23:44 ` [PATCH bpf-next v3 4/4] selftests/bpf: test_progs: remove unused ret Stanislav Fomichev
2019-08-27 22:44 ` [PATCH bpf-next v3 0/4] selftests/bpf: test_progs: misc fixes Daniel Borkmann
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=20190821234427.179886-1-sdf@google.com \
--to=sdf@google.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@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).