Comment 2 for bug 1851316

Here are unsuccessful and successful runs, respectively, with -v:

ubuntu@kzanol:~$ sudo stress-ng -k --aggressive --verify --timeout 30 --stack 0 -v
stress-ng: debug: [4498] 4 processors online, 4 processors configured
stress-ng: info: [4498] dispatching hogs: 4 stack
stress-ng: debug: [4498] cache allocate: default cache size: 3072K
stress-ng: debug: [4498] starting stressors
stress-ng: debug: [4499] stress-ng-stack: started [4499] (instance 0)
stress-ng: debug: [4500] stress-ng-stack: started [4500] (instance 1)
stress-ng: debug: [4498] 4 stressors spawned
stress-ng: debug: [4501] stress-ng-stack: started [4501] (instance 2)
stress-ng: debug: [4502] stress-ng-stack: started [4502] (instance 3)
stress-ng: debug: [4498] process [4499] (stress-ng-stack) terminated on signal: 11 (Segmentation fault)
stress-ng: debug: [4498] process [4499] terminated
stress-ng: debug: [4498] process [4500] (stress-ng-stack) terminated on signal: 11 (Segmentation fault)
stress-ng: debug: [4498] process [4500] terminated
stress-ng: debug: [4498] process [4501] (stress-ng-stack) terminated on signal: 11 (Segmentation fault)
stress-ng: debug: [4498] process [4501] terminated
stress-ng: debug: [4498] process [4502] (stress-ng-stack) terminated on signal: 11 (Segmentation fault)
stress-ng: debug: [4498] process [4502] terminated
stress-ng: info: [4498] unsuccessful run completed in 32.09s

ubuntu@kzanol:~$ sudo stress-ng -k --aggressive --verify --timeout 30 --stack 0 -v
stress-ng: debug: [4606] 4 processors online, 4 processors configured
stress-ng: info: [4606] dispatching hogs: 4 stack
stress-ng: debug: [4606] cache allocate: default cache size: 3072K
stress-ng: debug: [4606] starting stressors
stress-ng: debug: [4607] stress-ng-stack: started [4607] (instance 0)
stress-ng: debug: [4608] stress-ng-stack: started [4608] (instance 1)
stress-ng: debug: [4606] 4 stressors spawned
stress-ng: debug: [4609] stress-ng-stack: started [4609] (instance 2)
stress-ng: debug: [4610] stress-ng-stack: started [4610] (instance 3)
stress-ng: debug: [4607] stress-ng-stack: exited [4607] (instance 0)
stress-ng: debug: [4610] stress-ng-stack: exited [4610] (instance 3)
stress-ng: debug: [4608] stress-ng-stack: exited [4608] (instance 1)
stress-ng: debug: [4609] stress-ng-stack: exited [4609] (instance 2)
stress-ng: debug: [4606] process [4607] terminated
stress-ng: debug: [4606] process [4608] terminated
stress-ng: debug: [4606] process [4609] terminated
stress-ng: debug: [4606] process [4610] terminated
stress-ng: info: [4606] successful run completed in 32.27s

(I realized a bit late that our test script was being run as root, so I added "sudo" to these runs; but the pattern of success vs. failure doesn't seem to be affected by this change.)