From: Jakub Kicinski <kuba@kernel.org>
To: Sheena Mohan <sheenamo@google.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
pabeni@redhat.com, horms@kernel.org,
Willem de Bruijn <willemb@google.com>,
Max Yuan <maxyuan@google.com>, Pin-yen Lin <treapking@google.com>,
Harshitha Ramamurthy <hramamurthy@google.com>,
Joshua Washington <joshwash@google.com>,
Danny Gonzalez <digonzal@google.com>,
David Decotigny <decot@google.com>,
Brian Vazquez <brianvv@google.com>
Subject: Re: [ANN] Google's Netdev-CI for IDPF and GVE
Date: Fri, 29 May 2026 13:59:38 -0700 [thread overview]
Message-ID: <20260529135938.0ba988eb@kernel.org> (raw)
In-Reply-To: <CADWJPTsg5G21=hybo81+QHv0+g64d3a+6gGUaJSm1i7EttCUcw@mail.gmail.com>
On Fri, 29 May 2026 13:44:48 -0700 Sheena Mohan wrote:
> We are happy to share that Netdev-CI testing on both IDPF (running on
> Google Bare Metal) and GVE (running on Google Virtual Machines) is now
> up and running.
> This NIPA integration work enables executing kselftests against the
> current proposed net-next kernel branch on real hardware.
>
> Thanks to Danny, Max, and Pin-yen for their contributions!
>
> The test results and logs are available in:
>
> IDPF Results: https://idpf-netdev-nipa.static.usercontent.goog/json/results.json
> GVE Results: https://gve-netdev-nipa.static.usercontent.goog/json/results.json
Awesome stuff! Pulling the results now.
prev parent reply other threads:[~2026-05-29 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 20:44 [ANN] Google's Netdev-CI for IDPF and GVE Sheena Mohan
2026-05-29 20:59 ` Jakub Kicinski [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=20260529135938.0ba988eb@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=digonzal@google.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=joshwash@google.com \
--cc=maxyuan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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