Skip to contentSkip to conversation

intel: low timeout

TEST Jakub Kicinski 2 participants 4 messages Jun 27 – Jul 1

Subsystems (2)
lore
Share & tools
lore

Jakub Kicinski

author maintainer
#0 lore raw

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.

#1 lore raw
Quoted 6 lines · Jakub Kicinski

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:

Quoted 7 lines

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.

author maintainer
#2 lore raw
Quoted 11 lines · Adrian
Quoted 10 lines · Jakub Kicinski

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:

Quoted 8 lines
Quoted 3 lines

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!

Quoted 1 line

I'll later take a look on default behavior of runner in case of timeouts.

default behavior == pass/fail status for the test?

#3 lore raw
Quoted 18 lines · Jakub Kicinski
Quoted 17 lines · Adrian
Quoted 6 lines · Jakub Kicinski

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:

Quoted 7 lines

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,

Quoted 8 lines
Quoted 2 lines

I've increased timeout to 10 minutes per test run. It seems to help with XDP tests score.

Great, thank you!

Quoted 1 line

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.