From: Matthieu Baerts <matttbe@kernel.org>
To: Sheena Mohan <sheenamo@google.com>
Cc: Willem de Bruijn <willemb@google.com>,
Netdev <netdev@vger.kernel.org>, Jakub Kicinski <kuba@kernel.org>
Subject: [TEST] Google's Netdev-CI: a few flaky tests
Date: Fri, 23 Oct 2026 18:02:41 +0200 [thread overview]
Message-ID: <224334a7-150e-4794-af72-596c3821558c@kernel.org> (raw)
Hi Sheena,
I hope you are doing well.
While looking at the results on the Netdev CI for the Google runners, I
notice some tests are quite flaky or constantly failing. I marked them
as "ignored" on the Netdev CI while this is being investigated.
- IDPF: psp-py started to a month ago. I guess you are monitoring the
results, but then if it is normal, it might be easier if you block the
known bad tests from running on your side. Just in case, a few links:
https://netdev.bots.linux.dev/flakes.html?tn-needle=psp-py&br-pfx=net-next-hw&ld-remote=google-idpf
Because the previous branch didn't get tested, the regression might be
due to the modifications introduced in the previous branch as well:
https://netdev.bots.linux.dev/branch_deltas/net-next-hw-2026-09-23--16-00.html
https://netdev.bots.linux.dev/branch_deltas/net-next-hw-2026-09-23--08-00.html
- GVE: "queues-py" test started to fail recently: I *think* it is a
regression due to the following patch that has just been dropped, but
we will only know that in a couple of hours:
https://lore.kernel.org/20261021155611.68473-1-phx0fer@gmail.com
https://netdev.bots.linux.dev/contest.html?remote=google-gve&executor=gve-nipa&test=queues-py
https://netdev.bots.linux.dev/branch_deltas/net-next-hw-2026-10-22--00-00.html
- GVE: A few tests are unstable for a while and have been ignored: do
you mind looking at them, please?
https://netdev.bots.linux.dev/flakes.html?min-flip=0&pw-y=0&br-pfx=net-next-hw&ld-remote=google-gve
- IDPF: sometimes, it takes ~4h to run the results (+1h to start).
That's fine because we have a 6h window, but just wondering: is it
normal? (The GVE runner seems to start quicker, but I guess that's
because one is on bare metal and the other in a VM)
Thank you for your help!
Cheers,
Matt
next reply other threads:[~2026-10-23 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 16:02 Matthieu Baerts [this message]
2026-10-24 17:49 ` [TEST] Google's Netdev-CI: a few flaky tests Sheena Mohan
2026-10-26 16:41 ` Matthieu Baerts
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=224334a7-150e-4794-af72-596c3821558c@kernel.org \
--to=matttbe@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sheenamo@google.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox