Netdev List
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Sheena Mohan <sheenamo@google.com>
Cc: Netdev <netdev@vger.kernel.org>,
	Willem de Bruijn <willemb@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Pin-yen Lin <treapking@google.com>
Subject: Re: [TEST] Google's Netdev-CI: missing results
Date: Fri, 20 Nov 2026 10:08:45 +0100	[thread overview]
Message-ID: <0469d224-3baa-48c2-9d28-ac0d9fa2ec73@kernel.org> (raw)
In-Reply-To: <26fb4276-5615-45fb-9cb9-fa5e872d8e7b@kernel.org>

Hi Sheena,

(+ cc Pin-yen)

On 23/10/2026 17:52, Matthieu Baerts wrote:
> I'm working on the Netdev CI, and I notice that the runners on Google
> side are frequently missing results:
> 
> https://netdev.bots.linux.dev/flakes.html?tn-needle=google.*vlan-py&min-flip=0&br-pfx=net-next-hw
> 
> (Look at the non-coloured blocks.)
> 
> Is it normal? Do you mind looking at that please? :)
> 
> Note that when an active runner doesn't process a branch, we cannot mark
> the whole batch being validated as "not causing regression" because it
> is lacking some validations. So when this happens, the end result is
> marked as "pending". That's not an issue when it is once in a while, but
> here, it looks "too frequent" not to be reported.

Lately, it looks like the situation got worst: 3 days without results.
Because it is blocking all the other HW tests, I temporarily disabled
the two Google runners: results (if any) are still fetched, but ignored.

Do you mind improving the situation, please?

Cheers,
Matt

      reply	other threads:[~2026-11-20  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 15:52 [TEST] Google's Netdev-CI: missing results Matthieu Baerts
2026-11-20  9:08 ` Matthieu Baerts [this message]

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=0469d224-3baa-48c2-9d28-ac0d9fa2ec73@kernel.org \
    --to=matttbe@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sheenamo@google.com \
    --cc=treapking@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