stress-ng kill

[apaolillo]

From the documentation of stress-ng

Sending a SIGALRM, SIGINT or SIGHUP to stress-ng causes it to terminate all the stressor processes and ensures temporary files and shared memory segments are removed cleanly.

So I don't think stress-ng is at fault here.
Have you tried running it manually and using ctrl-c this should behave the same as trying to send SIGINT via benchkit.

If the problem only occurs within benchkit, I think the shell_async( might be to blame.
It uses os.setsid, which might be messing with the main pid of the stress-ng process.

Originally posted by @aaronbog in #237 (comment)