From: Jakub Kicinski <kuba@kernel.org>
To: Soham Chakradeo <sohamch.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, linux-kselftest@vger.kernel.org,
Soham Chakradeo <sohamch@google.com>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next 0/4] selftests/net: packetdrill: import multiple tests
Date: Wed, 18 Dec 2024 10:00:13 -0800 [thread overview]
Message-ID: <20241218100013.0c698629@kernel.org> (raw)
In-Reply-To: <20241217185203.297935-1-sohamch.kernel@gmail.com>
On Tue, 17 Dec 2024 18:51:57 +0000 Soham Chakradeo wrote:
> Import tests for the following features (folder names in brackets):
> ECN (ecn) : RFC 3168
> Close (close) : RFC 9293
> TCP_INFO (tcp_info) : RFC 9293
> Fast recovery (fast_recovery) : RFC 5681
> Timestamping (timestamping) : RFC 1323
> Nagle (nagle) : RFC 896
> Selective Acknowledgments (sack) : RFC 2018
> Recent Timestamp (ts_recent) : RFC 1323
> Send file (sendfile)
> Syscall bad arg (syscall_bad_arg)
> Validate (validate)
> Blocking (blocking)
> Splice (splice)
> End of record (eor)
> Limited transmit (limited_transmit)
Excellent, thanks for adding all these! I will merge the patches
momentarily but I do see a number of flakes on our VMs with debug
configs enabled:
https://netdev.bots.linux.dev/flakes.html?min-flip=0&tn-needle=packetdrill-dbg
In the 7 runs so far we got 2 flakes on:
tcp-timestamping-client-only-last-byte-pkt
tcp-fast-recovery-prr-ss-ack-below-snd-una-cubic-pkt
tcp-timestamping-server-pkt
1 flake on:
tcp-timestamping-partial-pkt
tcp-eor-no-coalesce-retrans-pkt
LMK if you can't find the outputs, they should be there within a couple
of clicks.
I'll set these cases to be ignored for now, but would be great if we
could find the way for them to be less time sensitive, perhaps?
next prev parent reply other threads:[~2024-12-18 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 18:51 [PATCH net-next 0/4] selftests/net: packetdrill: import multiple tests Soham Chakradeo
2024-12-17 18:51 ` [PATCH net-next 1/4] selftests/net: packetdrill: import tcp/ecn, tcp/close, tcp/sack, tcp/tcp_info Soham Chakradeo
2024-12-17 18:51 ` [PATCH net-next 2/4] selftests/net: packetdrill: import tcp/fast_recovery, tcp/nagle, tcp/timestamping Soham Chakradeo
2024-12-17 18:52 ` [PATCH net-next 3/4] selftests/net: packetdrill: import tcp/eor, tcp/splice, tcp/ts_recent, tcp/blocking Soham Chakradeo
2024-12-17 18:52 ` [PATCH net-next 4/4] selftests/net: packetdrill: import tcp/user_timeout, tcp/validate, tcp/sendfile, tcp/limited-transmit, tcp/syscall_bad_arg Soham Chakradeo
2024-12-18 18:00 ` Jakub Kicinski [this message]
2024-12-18 19:43 ` [PATCH net-next 0/4] selftests/net: packetdrill: import multiple tests Willem de Bruijn
2024-12-19 8:54 ` Paolo Abeni
2024-12-19 19:31 ` Willem de Bruijn
2024-12-20 2:01 ` Jakub Kicinski
2024-12-23 3:46 ` Willem de Bruijn
2024-12-23 16:50 ` Jakub Kicinski
2024-12-24 15:59 ` Willem de Bruijn
2024-12-27 18:41 ` Jakub Kicinski
2024-12-18 18:10 ` patchwork-bot+netdevbpf
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=20241218100013.0c698629@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sohamch.kernel@gmail.com \
--cc=sohamch@google.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox