From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH net-next] selftests: netconsole: print diagnostic on busywait timeout in netcons_basic
Date: Wed, 04 Mar 2026 01:30:34 +0000 [thread overview]
Message-ID: <177258783429.1546050.10122433930612295627.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260302-netconsole_test_verbose-v1-1-b1be5d30cd7d@debian.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 02 Mar 2026 06:40:39 -0800 you wrote:
> The script uses set -euo pipefail, so when busywait times out waiting
> for the netconsole message to arrive, it returns 1 and the script exits
> immediately without printing any error message. As reported by Jakub,
> this makes failures hard to diagnose since the test reports exit=1 with
> no explanation.
>
> Handle the busywait failure explicitly so that a FAIL message is printed
> before exiting. This is how it looks like now:
>
> [...]
Here is the summary with links:
- [net-next] selftests: netconsole: print diagnostic on busywait timeout in netcons_basic
https://git.kernel.org/netdev/net-next/c/dfa77c0dd4ab
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-03-04 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 14:40 [PATCH net-next] selftests: netconsole: print diagnostic on busywait timeout in netcons_basic Breno Leitao
2026-03-04 1: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=177258783429.1546050.10122433930612295627.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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