Apologies for taking so long to get back to you, this issue slipped past my radar. Some triaging questions:
1. How many CPUs are there on these machines? 2. Which version of stress-ng is being used? Thanks. I suspect that aggressive mode is running the stressors in such a way that the scheduling is not getting around to some of these stress processes and hence they are not getting a SIGALRM in a timely manner. -- 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
