stress-ng timed out and was forcefully terminated within CPU & Memory stress

[scotthu27]

Bug Description

stress-ng always timed out within CPU & Memory stress with new ver.: 0.21.02
timeout always reset to default value (86400) which make the CPU & Memory cannot be finished

Cert-blocker Test Case

• cert-blocker

To Reproduce

com.canonical.certification::stress/cpu_stress_ng_test
com.canonical.certification::stress/memory_stress_ng

Expected Result

supported stress-ng jobs should be run correctly

Actual Result

Running command: stress-ng --aggressive --verify --oom-avoid-bytes 10% --timeout 7200 --metrics-brief --tz --times --af-alg 0 --bsearch 0 --context 0 --cpu 0 --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 --matrix 0 --qsort 0 --str 0 --stream 0 --tsearch 0 --vecmath 0 --wcs 0
08 Jun 07:29: Running multiple stress-ng stressors in parallel for 7200
seconds...
** stress-ng timed out and was forcefully terminated

Running command: stress-ng --aggressive --verify --oom-avoid-bytes 10% --timeout 300  --mmapmany 0
08 Jun 12:31: Running stress-ng mmapmany stressor for 300 seconds...
** stress-ng timed out and was forcefully terminated

Environment

OS: Ubuntu 24.04.4
Checkbox Version: 7.2.0.dev22
Checkbox Type: Deb
stress-ng ver.: 0.21.02-1~n1

Relevant log output

Additional context

No response

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/CHECKBOX-2278.

This message was autogenerated

[gowthamhosamane]

Seeing the same behavior with,
Ubuntu 26.04
Checkbox version 7.3.0.dev42