Running with -a 0 will invoke every stressor with an instance on each CPU. Some of these stressors get I/O blocked or may be swapped out and blocked for a relatively long time before they get re-scheduled, and this can cause the timeout overrun. Stress tests are timed out using SIGALRM so it may be the case that some of the system calls that are blocked that are not interruptible have to be waited for before completion before the stressor is terminated. This cannot be fixed - it is a system behavioral issue that cannot be worked around.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826791 Title: stress-ng cpu tests run longer than configured timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1826791/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
