From: patchwork-bot+netdevbpf@kernel.org
To: Gregory Bell <grbell@redhat.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, eddyz87@gmail.com,
ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] selftests/bpf: fix flaky build_id test
Date: Thu, 19 Feb 2026 21:15:43 +0000 [thread overview]
Message-ID: <177153574378.67400.13045669900937971712.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1771338492.git.grbell@redhat.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 17 Feb 2026 09:32:35 -0500 you wrote:
> The build_id selftest intermittently fails with the following error:
>
> ./test_progs -t build_id/nofault-paged-out
> serial_test_build_id:PASS:parse_build_id 0 nsec
> subtest_nofault:PASS:skel_open 0 nsec
> subtest_nofault:PASS:link 0 nsec
> subtest_nofault:PASS:trigger_uprobe 0 nsec
> subtest_nofault:PASS:res 0 nsec
> subtest_nofault:FAIL:build_id_status unexpected build_id_status: actual 1 != expected 2
> 46/1 build_id/nofault-paged-out:FAIL
> 46 build_id:FAIL
> 397 stacktrace_build_id:OK
> 398 stacktrace_build_id_nmi:OK
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] selftests/bpf: fix flaky build_id test
https://git.kernel.org/bpf/bpf-next/c/d820fa311482
- [bpf-next,v2,2/2] selftests/bpf: align build_id test mapping to 64K page size
https://git.kernel.org/bpf/bpf-next/c/18a1d365e825
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-02-19 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 14:32 [PATCH bpf-next v2 0/2] selftests/bpf: fix flaky build_id test Gregory Bell
2026-02-17 14:32 ` [PATCH bpf-next v2 1/2] " Gregory Bell
2026-02-17 14:32 ` [PATCH bpf-next v2 2/2] selftests/bpf: align build_id test mapping to 64K page size Gregory Bell
2026-02-19 21:15 ` 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=177153574378.67400.13045669900937971712.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=grbell@redhat.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox