From: "Pielech, Adrian" <adrian.pielech@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <przemyslaw.kitszel@intel.com>,
<intel-wired-lan@lists.osuosl.org>, <anthony.l.nguyen@intel.com>,
<pabeni@redhat.com>, <davem@davemloft.net>, <edumazet@google.com>,
<horms@kernel.org>, <andrew+netdev@lunn.ch>,
<krzysztof.galazka@intel.com>
Subject: Re: [ANN] intel's netdev-ci for i40e
Date: Wed, 11 Feb 2026 10:17:52 +0100 [thread overview]
Message-ID: <54e57b6a-8cd6-4e2f-8ced-0cbb41c99e4e@intel.com> (raw)
In-Reply-To: <20260204174033.5aa7dc6a@kernel.org>
On 2/5/2026 2:40 AM, Jakub Kicinski wrote:
> On Wed, 4 Feb 2026 13:15:03 +0100 Pielech, Adrian wrote:
>> On 2/4/2026 4:08 AM, Jakub Kicinski wrote:
>>> Looks like the GRO test result parsing is off, the test cases are
>>> reported as for example:
>>>
>>> gro-test-lro-ipv6-ip-tos # XFAIL Device does not support...
>>>
>>> Looks like this affects all your runners, I haven't noticed earlier.
>>
>> I have fixed that, XFAIL should be reported as fail even if further
>> message suggests that the test should report SKIP due to "device does
>> not support...".
>>
>> Historical results were parsed again to remove test cases:
>> "[...] # XFAIL [...]".
>
> Looks good now, thanks!
>
> One more note, the "driver metadata" is currently reported as:
>
> {"devlink":{"driver":"i40e", ...
>
> looks like you have some extra nests there. That's perfectly fine,
> but we need there to be a "driver" key in the outmost object.
> Right now our UIs show "undefined" for the drivers here:
> https://netdev.bots.linux.dev/devices.html
I have moved position of "driver" from device.devlink.driver to
device.driver. Regenerated current and past results. You can refresh
your dashboard as well to wipe duplicated entries.
next prev parent reply other threads:[~2026-02-11 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 12:35 [ANN] intel's netdev-ci for i40e Pielech, Adrian
2026-02-04 3:08 ` Jakub Kicinski
2026-02-04 12:15 ` Pielech, Adrian
2026-02-05 1:40 ` Jakub Kicinski
2026-02-11 9:17 ` Pielech, Adrian [this message]
2026-02-11 16:26 ` Jakub Kicinski
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=54e57b6a-8cd6-4e2f-8ced-0cbb41c99e4e@intel.com \
--to=adrian.pielech@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=krzysztof.galazka@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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