* [TEST] intel: low timeout
@ 2026-06-27 16:54 Jakub Kicinski
2026-06-30 12:56 ` Pielech, Adrian
0 siblings, 1 reply; 4+ messages in thread
From: Jakub Kicinski @ 2026-06-27 16:54 UTC (permalink / raw)
To: Pielech, Adrian
Cc: Kitszel, Przemyslaw, netdev@vger.kernel.org, intel-wired-lan
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [TEST] intel: low timeout
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
0 siblings, 1 reply; 4+ messages in thread
From: Pielech, Adrian @ 2026-06-30 12:56 UTC (permalink / raw)
To: Jakub Kicinski
Cc: Kitszel, Przemyslaw, netdev@vger.kernel.org, intel-wired-lan,
leszek.pepiak
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.
I'll later take a look on default behavior of runner in case of timeouts.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [TEST] intel: low timeout
2026-06-30 12:56 ` Pielech, Adrian
@ 2026-06-30 22:50 ` Jakub Kicinski
2026-07-01 11:08 ` Pielech, Adrian
0 siblings, 1 reply; 4+ messages in thread
From: Jakub Kicinski @ 2026-06-30 22:50 UTC (permalink / raw)
To: Pielech, Adrian
Cc: Kitszel, Przemyslaw, netdev@vger.kernel.org, intel-wired-lan,
leszek.pepiak
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?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [TEST] intel: low timeout
2026-06-30 22:50 ` Jakub Kicinski
@ 2026-07-01 11:08 ` Pielech, Adrian
0 siblings, 0 replies; 4+ messages in thread
From: Pielech, Adrian @ 2026-07-01 11:08 UTC (permalink / raw)
To: Jakub Kicinski
Cc: Kitszel, Przemyslaw, netdev@vger.kernel.org, intel-wired-lan,
leszek.pepiak
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-07-01 11:08 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox