Comment 0 for bug 1858858

Discovered on 18.04 / 4.15 against both SSD and NVMe drives in this submission:
https://certification.canonical.com/hardware/201912-27596/submission/156320/test/64283/result/11844159/

Stress-NG spent 4 minutes attempting to run a stressor that "is not implemented on this system"

Running stress-ng aiol stressor for 240 seconds....
stress-ng: info:  [130482] dispatching hogs: 256 aiol
stress-ng: info:  [130483] stress-ng-aiol: this stressor is not implemented on this system: x86_64 Linux 4.15.0-72-generic gcc 7.4
stress-ng: info:  [130484] stress-ng-aiol: this stressor is not implemented on this system: x86_64 Linux 4.15.0-72-generic gcc 7.4
stress-ng: info:  [130485] stress-ng-aiol: this stressor is not implemented on this system: x86_64 Linux 4.15.0-72-generic gcc 7.4
...
stress-ng: info:  [130737] stress-ng-aiol: this stressor is not implemented on this system: x86_64 Linux 4.15.0-72-generic gcc 7.4
stress-ng: info:  [130738] stress-ng-aiol: this stressor is not implemented on this system: x86_64 Linux 4.15.0-72-generic gcc 7.4
stress-ng: info:  [130482] successful run completed in 240.04s (4 mins, 0.04 secs)

This did not affect the outcome of the testing, so only a minor issue of confusing output because it actually consumed 4 minutes of runtime on something that appears to not be supported.

the command line that would have been used is found in the disk_stress_ng script in checkbox and is:

stress-ng --aggressive --verify --timeout 240 --temp-path $test_dir --aiol 0 --hdd-opts dsync --readahead-bytes 16M -k