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: missing results
Date: Fri, 23 Oct 2026 20:12:53 +0200 [thread overview]
Message-ID: <374b4465-8b45-4285-93aa-533a4a0cff33@kernel.org> (raw)
Hi Adrian, Przemyslaw,
I'm working on the Netdev CI, and it looks like the Intel runners are
frequently missing results:
https://netdev.bots.linux.dev/flakes.html?tn-needle=intel&min-flip=0&pw-n=0&br-pfx=net-next-hw
(Look at the non-coloured blocks.)
It is not very frequent -- once a week -- and when this happens, usually
all runners/executors are missing, but 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
better checking why some results are missing.
Cheers,
Matt
reply other threads:[~2026-10-23 18:12 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=374b4465-8b45-4285-93aa-533a4a0cff33@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox