From: Matthieu Baerts <matttbe@kernel.org>
To: Gustavo Padovan <gus@collabora.com>
Cc: Netdev <netdev@vger.kernel.org>, Jakub Kicinski <kuba@kernel.org>
Subject: [TEST] Collabora's Netdev-CI: missing results
Date: Fri, 23 Oct 2026 20:02:27 +0200 [thread overview]
Message-ID: <861390d1-1fdc-4dcc-a431-236ddca42dfd@kernel.org> (raw)
Hi Gustavo,
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.
Cheers,
Matt
reply other threads:[~2026-10-23 18:02 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=861390d1-1fdc-4dcc-a431-236ddca42dfd@kernel.org \
--to=matttbe@kernel.org \
--cc=gus@collabora.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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