All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Adrian Pielech <adrian.pielech@intel.com>,
	Przemyslaw Kitszel <przemyslaw.kitszel@intel.com>
Cc: Netdev <netdev@vger.kernel.org>, Jakub Kicinski <kuba@kernel.org>
Subject: [TEST] Intel's Netdev-CI: a few flaky tests
Date: Fri, 23 Oct 2026 20:30:06 +0200	[thread overview]
Message-ID: <5aec31d5-d042-4263-b3df-fa5a6a1399ec@kernel.org> (raw)

Hi Adrian, Przemyslaw,

I hope you are doing well.

While looking at the results on the Netdev CI for the Intel runners, I
noticed some tests are quite flaky or constantly failing. I marked them
as "ignored" on the Netdev CI while this is being investigated.

 https://netdev.bots.linux.dev/flakes.html?tn-needle=intel&pw-y=0&br-pfx=net-next-hw

Do you mind looking at them, please? :)


Regarding tests that are constantly failing, I guess you are monitoring
the results, and you noticed that gro_sw.py is failing most of the time
on XL710 (i40e). If it is normal, it might be easier if you block the
known bad tests from running on your side. Note that around September,
there was a split of gro.py into gro_hw.py and gro_sw.py:

 https://netdev.bots.linux.dev/contest.html?remote=intel-i40e&executor=i40e-XL710-Q2&test=gro-sw-py

(gro.py was failing before)


While at it, some tests running in our lab with Intel NICs are also
flaky. Maybe that's due to the same issues?

 https://netdev.bots.linux.dev/flakes.html?tn-needle=netdev-(E810%7CX710)&pw-y=0&br-pfx=net-next-hw


Thank you for your help!

Cheers,
Matt

                 reply	other threads:[~2026-10-23 18:30 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=5aec31d5-d042-4263-b3df-fa5a6a1399ec@kernel.org \
    --to=matttbe@kernel.org \
    --cc=adrian.pielech@intel.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.