stress-ng does end after set time with -t or --timeout

[Elias Aarnio]

Expected behaviour when running

stress-ng --class cpu --sequential 4 --timeout 30s -v --tz

or

stress-ng --class cpu --sequential 4 -t 30 -v --tz

is the test should stop after 30 seconds.

The test goes on until user does CTRL-C in terminal window.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: stress-ng 0.05.23-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec 4 13:57:27 2017
InstallationDate: Installed on 2017-11-27 (6 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS (Finnish Remix) "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: stress-ng
UpgradeStatus: No upgrade log present (probably fresh install)

[Colin Ian King (colin-king)]

The command 'stress-ng --class cpu --sequential 4 --timeout 30s -v --tz' informs stress-ng to run each of the CPU class of stressors for 30 seconds per stressor.

Given that the af-alg bsearch context cpu cpu-online crypt fp-error getrandom heapsort hsearch longjmp lsearch matrix mergesort numa qsort rdrand str stream tsc tsearch vecmath wcs zlib CPU class of stressors will be run, that's a total of 24 stressors, or 24 x 30 seconds, or 12 minutes run in total, give or take a few seconds.

Are you seeing this behavior?

[Elias Aarnio (elias-aarnio)]

Yes, I am seeing this behaviour. My mistake - I did not understand that the -t or --timeout define the length of test using one type of stressor, not the length of the whole test.