Netdev List
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Gustavo Padovan <gus@collabora.com>
Cc: Netdev <netdev@vger.kernel.org>, Jakub Kicinski <kuba@kernel.org>,
	Aurelien Aptel <aaptel@nvidia.com>,
	Shai Malin <smalin@nvidia.com>,
	Boris Pismenny <borisp@nvidia.com>,
	Or Gerlitz <ogerlitz@nvidia.com>, Yoray Zack <yorayz@nvidia.com>,
	Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [TEST] Collabora's Netdev-CI: missing results
Date: Fri, 20 Nov 2026 10:16:16 +0100	[thread overview]
Message-ID: <2acf8e3c-9f9b-4784-afaa-9cc0e78c893b@kernel.org> (raw)
In-Reply-To: <861390d1-1fdc-4dcc-a431-236ddca42dfd@kernel.org>

Hi Gustavo,

(+cc nvidia people who worked on nvme-tcp from [1])

On 23/10/2026 20:02, Matthieu Baerts wrote:
> I'm working on the Netdev CI, and it looks like the Nvidia NVME runner
> on Collabora's side is frequently missing results:
> 
> https://netdev.bots.linux.dev/flakes.html?tn-needle=collabora-nvidia-nvme&min-flip=0&br-pfx=net-next-hw
> 
> (Look at the non-coloured blocks.)
> 
> Is it normal? Do you mind looking at that please? :)
> 
> I hope you are the right person to contact for this kind of issues. If
> not, could you please Cc the right people please?
> 
> Apart from that, the single test seems to be stable!
> 
> 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.

Sorry for the ping, but any news on your side about that?

The "collabora-nvidia-nvme" is still disabled on NIPA: results (if any)
are still fetched, but ignored. It would be nice to re-enable it once it
is more reliable.

[1] https://lore.kernel.org/20250430085741.5108-1-aaptel@nvidia.com

Cheers,
Matt

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 18:02 [TEST] Collabora's Netdev-CI: missing results Matthieu Baerts
2026-11-20  9:16 ` 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=2acf8e3c-9f9b-4784-afaa-9cc0e78c893b@kernel.org \
    --to=matttbe@kernel.org \
    --cc=aaptel@nvidia.com \
    --cc=borisp@nvidia.com \
    --cc=gus@collabora.com \
    --cc=kuba@kernel.org \
    --cc=mgurtovoy@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@nvidia.com \
    --cc=smalin@nvidia.com \
    --cc=yorayz@nvidia.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