netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Simon Horman <horms@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
	 Florian Westphal <fw@strlen.de>,
	Hangbin Liu <liuhangbin@gmail.com>,
	 Jaehee Park <jhpark1013@gmail.com>,
	Petr Machata <petrm@nvidia.com>,
	 Nikolay Aleksandrov <razor@blackwall.org>,
	 Ido Schimmel <idosch@nvidia.com>,
	 Davide Caratti <dcaratti@redhat.com>,
	 Matthieu Baerts <matttbe@kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [TEST] Flake report
Date: Tue, 14 May 2024 09:52:18 -0400	[thread overview]
Message-ID: <f7ta5ks7b71.fsf@redhat.com> (raw)
In-Reply-To: <20240511132724.GF2347895@kernel.org> (Simon Horman's message of "Sat, 11 May 2024 14:27:24 +0100")

Simon Horman <horms@kernel.org> writes:

> + Aaron
>
> On Thu, May 09, 2024 at 04:09:58PM -0700, Jakub Kicinski wrote:
>> Hi!
>> 
>> Feels like the efforts to get rid of flaky tests have slowed down a bit,
>> so I thought I'd poke people..
>> 
>> Here's the full list:
>> https://netdev.bots.linux.dev/flakes.html?min-flip=0&pw-y=0
>> click on test name to get the list of runs and links to outputs.
>> 
>> As a reminder please see these instructions for repro:
>> https://github.com/linux-netdev/nipa/wiki/How-to-run-netdev-selftests-CI-style
>> 
>> I'll try to tag folks who touched the tests most recently, but please
>> don't hesitate to chime in.
>> 
>> 
>> net
>> ---
>> 
>> arp-ndisc-untracked-subnets-sh
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> To: Jaehee Park <jhpark1013@gmail.com>
>> Cc: Hangbin Liu <liuhangbin@gmail.com>
>> 
>> Times out on debug kernels, passes on non-debug.
>> This is a real timeout, eats full 7200 seconds.
>> 
>> xfrm-policy-sh
>> ~~~~~~~~~~~~~~
>> To: Hangbin Liu <liuhangbin@gmail.com>
>> 
>> Times out on debug kernels, passed on non-debug,
>> This is a "inactivity" timeout, test doesn't print anything
>> for 900 seconds so the runner kills it. We can bump the timeout
>> but not printing for 15min is bad..
>> 
>> cmsg-time-sh
>> ~~~~~~~~~~~~
>> To: Jakub Kicinski <kuba@kernel.org> (forgot I wrote this :D)
>> 
>> Fails randomly.
>> 
>> pmtu-sh
>> ~~~~~~~
>> To: Simon Horman <horms@kernel.org>
>> 
>> Skipped because it wants full OVS tooling.
>
> My understanding is that Aaron (CCed) is working on addressing
> this problem by allowing the test to run without full OVS tooling.

Yes.

>> forwarding
>> ----------
>> 
>> sch-tbf-ets-sh, sch-tbf-prio-sh
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> To: Petr Machata <petrm@nvidia.com>
>> 
>> These fail way too often on non-debug kernels :(
>> Perhaps we can extend the lower bound?
>> 
>> bridge-igmp-sh, bridge-mld-sh
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> To: Nikolay Aleksandrov <razor@blackwall.org>
>> Cc: Ido Schimmel <idosch@nvidia.com>
>> 
>> On debug kernels it always fails with:
>> 
>> # TEST: IGMPv3 group 239.10.10.10 exclude timeout                     [FAIL]
>> # Entry 192.0.2.21 has blocked flag failed
>> 
>> For MLD:
>> 
>> # TEST: MLDv2 group ff02::cc exclude timeout                          [FAIL]
>> # Entry 2001:db8:1::21 has blocked flag failed
>> 
>> vxlan-bridge-1d-sh
>> ~~~~~~~~~~~~~~~~~~
>> To: Ido Schimmel <idosch@nvidia.com>
>> Cc: Petr Machata <petrm@nvidia.com>
>> 
>> Flake fails almost always, with some form of "Expected to capture 0
>> packets, got $X"
>> 
>> mirror-gre-lag-lacp-sh
>> ~~~~~~~~~~~~~~~~~~~~~~
>> To: Petr Machata <petrm@nvidia.com>
>> 
>> Often fails on debug with:
>> 
>> # TEST: mirror to gretap: LAG first slave (skip_hw)                   [FAIL]
>> # Expected to capture 10 packets, got 13.
>> 
>> mirror-gre-vlan-bridge-1q-sh, mirror-gre-bridge-1d-vlan-sh
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> To: Petr Machata <petrm@nvidia.com>
>> 
>> Same kind of failure as above but less often and both on debug and non-debug.
>> 
>> tc-actions-sh
>> ~~~~~~~~~~~~~
>> To: Davide Caratti <dcaratti@redhat.com>
>> 
>> It triggers a random unhandled interrupt, somehow (look at stderr).
>> It's the only test that does that.
>> 
>> 
>> mptcp
>> -----
>> To: Matthieu Baerts <matttbe@kernel.org>
>> 
>> simult-flows-sh is still quite flaky :(
>> 
>> 
>> nf
>> --
>> To: Florian Westphal <fw@strlen.de>
>> 
>> These are skipped because of some compatibility issues:
>> 
>>  nft-flowtable-sh, bridge-brouter-sh, nft-audit-sh
>> 
>> Please LMK if I need to update the CLI tooling. 
>> Or is this missing kernel config?
>> 


  reply	other threads:[~2024-05-14 13:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 23:09 [TEST] Flake report Jakub Kicinski
2024-05-10  3:24 ` Hangbin Liu
2024-05-10  8:35 ` Florian Westphal
2024-05-10 14:47   ` Jakub Kicinski
2024-05-10 16:03     ` Jakub Kicinski
2024-05-10 16:41       ` Florian Westphal
2024-05-10 18:02         ` Jakub Kicinski
2024-05-11  0:14           ` Jakub Kicinski
2024-05-11  6:50             ` Florian Westphal
2024-05-10 14:28 ` Matthieu Baerts
2024-05-30 17:35   ` Matthieu Baerts
2024-05-30 17:41     ` Jakub Kicinski
2024-05-31  7:52       ` Matthieu Baerts
2024-05-10 14:45 ` Nikolay Aleksandrov
2024-05-11 13:27 ` Simon Horman
2024-05-14 13:52   ` Aaron Conole [this message]
2024-05-13 11:58 ` Davide Caratti
2024-05-13 16:52 ` Petr Machata
2024-05-14 13:43   ` Jakub Kicinski
2024-05-21 16:29   ` Petr Machata

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=f7ta5ks7b71.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=dcaratti@redhat.com \
    --cc=fw@strlen.de \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=jhpark1013@gmail.com \
    --cc=kuba@kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=matttbe@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.com \
    --cc=razor@blackwall.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;
as well as URLs for NNTP newsgroup(s).