From: patchwork-bot+netdevbpf@kernel.org
To: Mykola Lysenko <mykolal@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next] selftests/bpf: refactor prog_tests logging and test execution
Date: Tue, 19 Apr 2022 04:30:11 +0000 [thread overview]
Message-ID: <165034261127.2677.996654647949648125.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220418222507.1726259-1-mykolal@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 18 Apr 2022 15:25:07 -0700 you wrote:
> This is a pre-req to add separate logging for each subtest in
> test_progs.
>
> Move all the mutable test data to the test_result struct.
> Move per-test init/de-init into the run_one_test function.
> Consolidate data aggregation and final log output in
> calculate_and_print_summary function.
> As a side effect, this patch fixes double counting of errors
> for subtests and possible duplicate output of subtest log
> on failures.
>
> [...]
Here is the summary with links:
- [v2,bpf-next] selftests/bpf: refactor prog_tests logging and test execution
https://git.kernel.org/bpf/bpf-next/c/2324257dbd68
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-19 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 22:25 [PATCH v2 bpf-next] selftests/bpf: refactor prog_tests logging and test execution Mykola Lysenko
2022-04-19 4:27 ` Andrii Nakryiko
2022-04-19 4:30 ` patchwork-bot+netdevbpf [this message]
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=165034261127.2677.996654647949648125.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=mykolal@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.