From: Matthieu Baerts <matttbe@kernel.org>
To: Pin-yen Lin <treapking@google.com>
Cc: Sheena Mohan <sheenamo@google.com>,
Willem de Bruijn <willemb@google.com>,
Netdev <netdev@vger.kernel.org>, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [TEST] Google's Netdev-CI: a few flaky tests
Date: Fri, 20 Nov 2026 10:09:46 +0100 [thread overview]
Message-ID: <8093f0a0-3a87-4cd6-9c53-e575007a9762@kernel.org> (raw)
In-Reply-To: <CAHwYsiqOhntJR7D00vzRed1=eo+4xXnRdYtTD79zdL35RT9Kog@mail.gmail.com>
Hi Pin-yen,
Thank you for this email.
On 20/11/2026 04:12, Pin-yen Lin wrote:
> On Mon, Oct 26, 2026 at 9:41 AM Matthieu Baerts <matttbe@kernel.org> wrote:
>> On 24/10/2026 19:49, Sheena Mohan wrote:
(...)
>>> - napi-id-py & bond-options-sh: We will investigate both tests.
>>
>> When fixes are applied or unstable tests are blocked on your side, do
>> you mind pinging me so I can remove them from this ignore list, please?
>>
>> https://netdev.bots.linux.dev/contest/filters-hw.json
>
> Both napi-id-py and devmem-py should be fixed now given that [1] has
> been accepted and merged to net-next. Could you remove these two from
> the ignore list?
Thank you for the fix and the ping, I just removed these two tests, plus
psp-py for IDPF which seems to have been disabled on your side.
> The fix for bond-options-sh has been sent out as [2] and the
> discussions are still ongoing on the mailing list.
That's good, and the v1 already seems to help. Please ping me when the
new version is applied.
(Note: as mentioned on [1], the Google runners are currently disabled.)
[1] https://lore.kernel.org/0469d224-3baa-48c2-9d28-ac0d9fa2ec73@kernel.org
Cheers,
Matt
prev parent reply other threads:[~2026-11-20 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 16:02 [TEST] Google's Netdev-CI: a few flaky tests Matthieu Baerts
2026-10-24 17:49 ` Sheena Mohan
2026-10-26 16:41 ` Matthieu Baerts
2026-11-20 3:12 ` Pin-yen Lin
2026-11-20 9:09 ` 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=8093f0a0-3a87-4cd6-9c53-e575007a9762@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.