From: kernel test robot <oliver.sang@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Jakub Kicinski <kuba@kernel.org>,
David Ahern <dsahern@kernel.org>, <netdev@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [ipv6] dfd2ee086a: packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-after-idle_ipv6.fail
Date: Fri, 28 Jun 2024 10:05:07 +0800 [thread overview]
Message-ID: <202406280948.73d69176-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-after-idle_ipv6.fail" on:
commit: dfd2ee086a63c730022cb095576a8b3a5a752109 ("ipv6: make addrconf_wq single threaded")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master e5b3efbe1ab1793bb49ae07d56d0973267e65112]
[test failed on linux-next/master b992b79ca8bc336fa8e2c80990b5af80ed8f36fd]
in testcase: packetdrill
version: packetdrill-x86_64-31fbbb7-1_20240226
with following parameters:
compiler: gcc-13
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz (Skylake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
we noticed this is an ipv6 related change, we observed there are quite some
'-ipv6' tests failed on this commit quite persistently but keeps clean on
parent, e.g.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler:
lkp-skl-d08/packetdrill/debian-12-x86_64-20240206.cgz/x86_64-rhel-8.3-func/gcc-13
f5d59230ec26aa5e dfd2ee086a63c730022cb095576
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:30 70% 21:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-ack-per-1pkt_ipv6.fail
:30 90% 27:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-ack-per-2pkt-send-5pkt_ipv6.fail
:30 77% 23:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-ack-per-2pkt-send-6pkt_ipv6.fail
:30 83% 25:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-ack-per-2pkt_ipv6.fail
:30 90% 27:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-ack-per-4pkt_ipv6.fail
:30 70% 21:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-after-idle_ipv6.fail
:30 67% 20:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-after-win-update_ipv6.fail
:30 73% 22:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-app-limited-9-packets-out_ipv6.fail
:30 73% 22:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-app-limited_ipv6.fail
:30 53% 16:30 packetdrill.packetdrill/gtests/net/tcp/slow_start/slow-start-fq-ack-per-2pkt_ipv6.fail
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/202406280948.73d69176-oliver.sang@intel.com
below is just an example, more details are in [1]
OK [/lkp/benchmarks/packetdrill/gtests/net/tcp/slow_start/slow-start-after-idle.pkt (ipv4)] <-- ok
stdout:
stderr:
FAIL [/lkp/benchmarks/packetdrill/gtests/net/tcp/slow_start/slow-start-after-idle.pkt (ipv6)] <-- fail
stdout:
stderr:
OK [/lkp/benchmarks/packetdrill/gtests/net/tcp/splice/tcp_splice_loop_test.pkt (ipv4)]
[1]
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240628/202406280948.73d69176-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-28 2:05 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=202406280948.73d69176-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.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