Netdev List
 help / color / mirror / Atom feed
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: Wed, 12 Aug 2026 15:43:44 -0700	[thread overview]
Message-ID: <20260812154344.39afcf7f@kernel.org> (raw)
In-Reply-To: <20260812145422.049f49fb@kernel.org>

On Wed, 12 Aug 2026 14:54:22 -0700 Jakub Kicinski wrote:
> BTW I noted that the branches tested are a bit spotty.
> The gve manifest only has results for around 33% of the branches 
> over the last 3 days. Some of the results are nul so the run hasn't
> completed.

To be clear -- some of the results are nul, but majority of the missing
branches are completely missing.

> idpf runner looks better but is also missing around one branch a day.
> 
> Is this something you're tracking?

  reply	other threads:[~2026-08-12 22:43 UTC|newest]

Thread overview: 11+ 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
2026-06-01 15:04   ` Jakub Kicinski
2026-06-01 20:42     ` Sheena Mohan
2026-06-19 18:59 ` Jakub Kicinski
2026-07-16 23:15   ` Sheena Mohan
2026-08-04 14:16     ` Jakub Kicinski
2026-08-12 20:56       ` Sheena Mohan
2026-08-12 21:54         ` Jakub Kicinski
2026-08-12 22:43           ` Jakub Kicinski [this message]
2026-08-13  0:49             ` Sheena Mohan

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=20260812154344.39afcf7f@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