It looks like the recent change in stress-ng is the cause to this problem.
The test has passed on the very same node with the same kernel on Jun. 15. But it has failed with the test executed today.
chroot STARTING
chroot RETURNED 2
chroot FAILED
stress-ng: debug: [12135] 1 processor online, 1 processor configured
stress-ng: info: [12135] dispatching hogs: 4 chroot
stress-ng: debug: [12135] cache allocate: default cache size: 56320K
stress-ng: debug: [12135] starting stressors
stress-ng: debug: [12135] 4 stressors spawned
stress-ng: debug: [12139] stress-ng-chroot: started [12139] (instance 3)
stress-ng: debug: [12138] stress-ng-chroot: started [12138] (instance 2)
stress-ng: debug: [12137] stress-ng-chroot: started [12137] (instance 1)
stress-ng: debug: [12136] stress-ng-chroot: started [12136] (instance 0)
stress-ng: debug: [12139] stress-ng-chroot: exited [12139] (instance 3)
stress-ng: debug: [12138] stress-ng-chroot: exited [12138] (instance 2)
stress-ng: debug: [12137] stress-ng-chroot: exited [12137] (instance 1)
stress-ng: debug: [12136] stress-ng-chroot: exited [12136] (instance 0)
stress-ng: error: [12135] process 12136 (stress-ng-chroot) terminated with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12135] process [12136] terminated
stress-ng: error: [12135] process 12137 (stress-ng-chroot) terminated with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12135] process [12137] terminated
stress-ng: error: [12135] process 12138 (stress-ng-chroot) terminated with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12135] process [12138] terminated
stress-ng: error: [12135] process 12139 (stress-ng-chroot) terminated with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12135] process [12139] terminated
stress-ng: info: [12135] unsuccessful run completed in 0.00s
Issue was introduced with child exit sanity checking http://
Fix committed: http://
author Colin Ian King <email address hidden> 2018-06-19 06:40:27 (GMT)
committer Colin Ian King <email address hidden> 2018-06-19 06:40:27 (GMT)
commit b72beabf372d27a
tree c7a268df07acb02
parent b580ecec2dbd75d
Don't exit child sub-processes with exit() (LP: #1777564)HEADmaster
When a child sub-process in any stressor exits with exit()
then the new atexit handler traps this as an illegal return
from the stressor and throws an error report. Avoid this
by exiting all stressor child sub-processes with _exit()
to skip the atexit handler.
Also fix up some exits that should be returns in stressors.
Signed-off-by: Colin Ian King <email address hidden>