From: "Pielech, Adrian" <adrian.pielech@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
<intel-wired-lan@lists.osuosl.org>, <leszek.pepiak@intel.com>
Subject: Re: [TEST] intel: low timeout
Date: Wed, 1 Jul 2026 13:08:37 +0200 [thread overview]
Message-ID: <dd1a53fe-4713-4e21-b854-cf6314915519@intel.com> (raw)
In-Reply-To: <20260630155022.27c9a271@kernel.org>
On 7/1/2026 12:50 AM, Jakub Kicinski wrote:
> On Tue, 30 Jun 2026 14:56:02 +0200 Pielech, Adrian wrote:
>> On 6/27/2026 6:54 PM, Jakub Kicinski wrote:
>>> Hi!
>>>
>>> Some of the tests need more than 5min, could you increase the timeout
>>> in the runner to 10 or 15min? Looks like it's hard-killing tests right
>>> now after 2min:
>>>
>>> https://netdev-ci-results.intel.com/ice-results/net-next-hw-2026-06-27--16-00/ice-E810-XXV4/xdp.py/stdout
>>>
>>> which leaks config across tests:
>>>
>>> https://netdev-ci-results.intel.com/ice-results/net-next-hw-2026-06-27--16-00/ice-E810-XXV4/irq.py/stdout
>>>
>>> BTW the JSON reports the timed out tests as pass.
>>
>> Hi Jakub,
>>
>> I've increased timeout to 10 minutes per test run. It seems to help with
>> XDP tests score.
>
> Great, thank you!
>
>> I'll later take a look on default behavior of runner in case of timeouts.
>
> default behavior == pass/fail status for the test?
Yes, pass/fail status selection. I've found the culprit and since next
run timeouts should be reported as fail.
prev parent reply other threads:[~2026-07-01 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 16:54 [TEST] intel: low timeout Jakub Kicinski
2026-06-30 12:56 ` Pielech, Adrian
2026-06-30 22:50 ` Jakub Kicinski
2026-07-01 11:08 ` Pielech, Adrian [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=dd1a53fe-4713-4e21-b854-cf6314915519@intel.com \
--to=adrian.pielech@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=leszek.pepiak@intel.com \
--cc=netdev@vger.kernel.org \
--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