stress-ng: when running with a large number of stressors and short timeout stats are wrong
Bug #1387104 reported by
Colin Ian King
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| stress-ng (Ubuntu) |
Fix Released
|
Medium
|
Colin Ian King | ||
Bug Description
We can have a situation where many stressors are invoked and the timeout kicks in before they are all successfully started. In these
cases it can be that the finish time has not been set because the process is not terminated (because it never started) and so we get
weird run time stats.
Related branches
| Changed in stress-ng (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Colin Ian King (colin-king) |
| Changed in stress-ng (Ubuntu): | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in stress-ng (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package stress-ng - 0.02.23-1
---------------
stress-ng (0.02.23-1) unstable; urgency=medium
* Makefile: bump version
* Initialise finish time in case it is never run (LP: #1387104)
* Add futex stressor (LP: #1386831)
-- Colin King <email address hidden> Wed, 29 Oct 2014 10:32:00 +0000