From: kernel test robot <oliver.sang@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [tcp] 614e8316aa: packetdrill.packetdrill/gtests/net/tcp/fastopen/server/client-ack-dropped-then-recovery-ms-timestamps_ipv4-mapped-v6.fail
Date: Mon, 30 Oct 2023 22:46:06 +0800 [thread overview]
Message-ID: <202310302216.f79d78bc-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "packetdrill.packetdrill/gtests/net/tcp/fastopen/server/client-ack-dropped-then-recovery-ms-timestamps_ipv4-mapped-v6.fail" on:
(in fact, we noticed 3 tests failed on this commit with high rate, but keep
clean on parent
af7721448a609d19 614e8316aa4cafba3e204cb8ee4
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:20 55% 11:20 packetdrill.packetdrill/gtests/net/tcp/fastopen/server/client-ack-dropped-then-recovery-ms-timestamps_ipv4-mapped-v6.fail
:20 70% 14:20 packetdrill.packetdrill/gtests/net/tcp/fastopen/server/client-ack-dropped-then-recovery-ms-timestamps_ipv4.fail
:20 45% 9:20 packetdrill.packetdrill/gtests/net/tcp/fastopen/server/client-ack-dropped-then-recovery-ms-timestamps_ipv6.fail
)
commit: 614e8316aa4cafba3e204cb8ee48bd12b92f3d93 ("tcp: add support for usec resolution in TCP TS values")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 66f1e1ea3548378ff6387b1ce0b40955d54e86aa]
in testcase: packetdrill
version: packetdrill-x86_64-31fbbb7-1_20231004
with following parameters:
compiler: gcc-12
test machine: 16 threads 1 sockets Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz (Broadwell-DE) with 48G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202310302216.f79d78bc-oliver.sang@intel.com
...
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/fastopen/server/client-ack-dropped-then-recovery-ms-timestamps.pkt (ipv6)]
...
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/fastopen/server/client-ack-dropped-then-recovery-ms-timestamps.pkt (ipv4-mapped-v6)]
...
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/fastopen/server/client-ack-dropped-then-recovery-ms-timestamps.pkt (ipv4)]
...
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231030/202310302216.f79d78bc-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-30 14:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202310302216.f79d78bc-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.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