From: patchwork-bot+netdevbpf@kernel.org
To: Dmitry Safonov <0x7f454c46@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net/selftests: Add loopback link local route for self-connect
Date: Thu, 03 Apr 2025 22:20:38 +0000 [thread overview]
Message-ID: <174371883849.2702664.8391877286405723636.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250402-tcp-ao-selfconnect-flake-v1-1-8388d629ef3d@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 02 Apr 2025 01:59:31 +0100 you wrote:
> From: Dmitry Safonov <0x7f454c46@gmail.com>
>
> self-connect-ipv6 got slightly flaky on netdev:
> > # timeout set to 120
> > # selftests: net/tcp_ao: self-connect_ipv6
> > # 1..5
> > # # 708[lib/setup.c:250] rand seed 1742872572
> > # TAP version 13
> > # # 708[lib/proc.c:213] Snmp6 Ip6OutNoRoutes: 0 => 1
> > # not ok 1 # error 708[self-connect.c:70] failed to connect()
> > # ok 2 No unexpected trace events during the test run
> > # # Planned tests != run tests (5 != 2)
> > # # Totals: pass:1 fail:0 xfail:0 xpass:0 skip:0 error:1
> > ok 1 selftests: net/tcp_ao: self-connect_ipv6
>
> [...]
Here is the summary with links:
- [net-next] net/selftests: Add loopback link local route for self-connect
https://git.kernel.org/netdev/net/c/e5ddf19dbc3e
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:[~2025-04-03 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 0:59 Dmitry Safonov via B4 Relay
2025-04-03 22:20 ` 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=174371883849.2702664.8391877286405723636.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.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
all inboxes | Powered by JetHome®