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: [Intel-wired-lan] [ANN] intel's netdev-ci for i40e
Date: Wed, 4 Feb 2026 13:15:03 +0100 [thread overview]
Message-ID: <a29bc22b-a1e3-4a9e-a63c-5d1c71a6f08b@intel.com> (raw)
In-Reply-To: <20260203190811.1f9e7530@kernel.org>
On 2/4/2026 4:08 AM, Jakub Kicinski wrote:
> On Tue, 3 Feb 2026 13:35:11 +0100 Pielech, Adrian wrote:
>> Hi folks,
>>
>> I'm pleased to announce that we have set up infrastructure for testing
>> netdev on our e700 NIC (i40e), which extends our current engagement with
>> e810 NICs(ice).
>>
>> This work plugs into netdev-ci initiative by netdev maintainers to run
>> kselftests against current proposed net-next-hw branch on real hardware.
>>
>> Our results are here:
>> https://netdev-ci-results.intel.com/i40e-results/results.json
>>
>> Human friendly results browser:
>> https://netdev-ci-results.intel.com/results_browser/index.html?drv=i40e
>
> Excellent!
>
> 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 [...]".
next prev parent reply other threads:[~2026-02-04 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 12:35 [Intel-wired-lan] [ANN] intel's netdev-ci for i40e Pielech, Adrian
2026-02-04 3:08 ` Jakub Kicinski
2026-02-04 12:15 ` Pielech, Adrian [this message]
2026-02-05 1:40 ` Jakub Kicinski
2026-02-11 9:17 ` Pielech, Adrian
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=a29bc22b-a1e3-4a9e-a63c-5d1c71a6f08b@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