Comment 4 for bug 1807732

https://certification.canonical.com/hardware/201908-27259/submission/148999/test/62536/result/11200424/

Reopened this as it seems those messages in MMAP still appear as Errors not Info:

Running stress-ng mmap stressor for 20460 seconds....
stress-ng: info: [5769] dispatching hogs: 96 mmap
stress-ng: error: [5826] stress-ng-mmap: gave up trying to mmap, no available memory
stress-ng: fail: [5818] stress-ng-mmap: rmdir './tmp-stress-ng-mmap-5818-26' failed, errno=2 (No such file or directory)
stress-ng: error: [5803] stress-ng-mmap: gave up trying to mmap, no available memory
stress-ng: fail: [5795] stress-ng-mmap: rmdir './tmp-stress-ng-mmap-5795-14' failed, errno=2 (No such file or directory)
stress-ng: error: [5864] stress-ng-mmap: gave up trying to mmap, no available memory
stress-ng: fail: [5842] stress-ng-mmap: rmdir './tmp-stress-ng-mmap-5842-39' failed, errno=2 (No such file or directory)
stress-ng: error: [5955] stress-ng-mmap: gave up trying to mmap, no available memory
stress-ng: fail: [5897] stress-ng-mmap: rmdir './tmp-stress-ng-mmap-5897-69' failed, errno=2 (No such file or directory)

Just for fun, also, this was run against 2TB of RAM w/ 3TB of swap space. Is it possible that those tmpdir isses are related to filing up the root filesystem?