From: kernel test robot <oliver.sang@intel.com>
To: Mahdi Arghavani <ma.arghavani@yahoo.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jason Xing <kerneljasonxing@gmail.com>,
Neal Cardwell <ncardwell@google.com>,
"Eric Dumazet" <edumazet@google.com>,
Haibo Zhang <haibo.zhang@otago.ac.nz>,
"David Eyers" <david.eyers@otago.ac.nz>,
Abbas Arghavani <abbas.arghavani@mdu.se>,
<netdev@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [tcp_cubic] 25c1a9ca53: packetdrill.packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k-idle-restart_ipv4-mapped-v6.fail
Date: Sun, 26 Jan 2025 14:30:05 +0800 [thread overview]
Message-ID: <202501261315.c6c7dbb4-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "packetdrill.packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k-idle-restart_ipv4-mapped-v6.fail" on:
(
in fact, there are other failed cases which can pass on parent:
4395a44acb15850e 25c1a9ca53db5780757e7f53e68
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:6 100% 6:6 packetdrill.packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k-idle-restart_ipv4-mapped-v6.fail
:6 100% 6:6 packetdrill.packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k-idle-restart_ipv4.fail
:6 100% 6:6 packetdrill.packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k-idle-restart_ipv6.fail
:6 100% 6:6 packetdrill.packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k_ipv4-mapped-v6.fail
:6 100% 6:6 packetdrill.packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k_ipv4.fail
:6 100% 6:6 packetdrill.packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k_ipv6.fail
)
commit: 25c1a9ca53db5780757e7f53e688b8f916821baa ("tcp_cubic: fix incorrect HyStart round start detection")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 405057718a1f9074133979a9f2ff0c9fa4a19948]
[test failed on linux-next/master 5ffa57f6eecefababb8cbe327222ef171943b183]
in testcase: packetdrill
version: packetdrill-x86_64-8d63bbc-1_20250115
with following parameters:
config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 8G 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/202501261315.c6c7dbb4-lkp@intel.com
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k-idle-restart.pkt (ipv4-mapped-v6)]
stdout:
20
30
36
stderr:
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k-idle-restart.pkt (ipv6)]
stdout:
20
30
36
stderr:
...
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k-idle-restart.pkt (ipv4)]
stdout:
20
30
36
stderr:
...
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k.pkt (ipv4)]
stdout:
20
30
36
stderr:
...
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k.pkt (ipv4-mapped-v6)]
stdout:
20
30
36
stderr:
...
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k.pkt (ipv6)]
stdout:
20
30
36
stderr:
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250126/202501261315.c6c7dbb4-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-01-26 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 6:30 kernel test robot [this message]
2025-01-26 8:49 ` [linus:master] [tcp_cubic] 25c1a9ca53: packetdrill.packetdrill/gtests/net/tcp/cubic/cubic-bulk-166k-idle-restart_ipv4-mapped-v6.fail Jason Xing
2025-01-27 10:19 ` Jason Xing
2025-01-27 15:03 ` Neal Cardwell
2025-01-27 23:30 ` Jason Xing
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=202501261315.c6c7dbb4-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=abbas.arghavani@mdu.se \
--cc=davem@davemloft.net \
--cc=david.eyers@otago.ac.nz \
--cc=edumazet@google.com \
--cc=haibo.zhang@otago.ac.nz \
--cc=kerneljasonxing@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ma.arghavani@yahoo.com \
--cc=ncardwell@google.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