From: patchwork-bot+netdevbpf@kernel.org
To: Vineet Gupta <vineet.gupta@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
memxor@gmail.com, emil@etsalapatis.com, ihor.solodrai@linux.dev,
shuah@kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: don't count skipped reg_bounds cases as skipped tests
Date: Sun, 01 Nov 2026 01:00:04 +0000 [thread overview]
Message-ID: <179349480431.2292683.4825596703739217680.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261028211921.1055711-1-vineet.gupta@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 28 Oct 2026 14:19:21 -0700 you wrote:
> test_progs-bpf_gcc reports an order of magnitude more skipped tests than it
> lists. A recent bpf-next run ends with
>
> Summary: 720/6383 PASSED, 8392 SKIPPED, 105/368 FAILED
>
> but the log for that same run names only 684 skipped subtests which are
> all accounted for; the other ~7700 are just ghosts.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: don't count skipped reg_bounds cases as skipped tests
https://git.kernel.org/bpf/bpf-next/c/a30c772627b2
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:[~2026-11-01 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 21:19 [PATCH bpf-next] selftests/bpf: don't count skipped reg_bounds cases as skipped tests Vineet Gupta
2026-11-01 0:59 ` Alexei Starovoitov
2026-11-01 1:00 ` 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=179349480431.2292683.4825596703739217680.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=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=vineet.gupta@linux.dev \
--cc=yonghong.song@linux.dev \
/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.