providers/base/bin/stress-ng-test.py Provide the exact command executed for each stressor (New)

[bladernr]

Provide the exact command executed for each stressor or set of stressors. Fixes CHECKBOX-1734

Description

Short addition to provide the exact command checkbox runs for a given stressor or set of stressors in the stress-ng tests to make it easier to later re-run a single stressor by hand when investigating failures.

Resolved issues

Resolves CHECKBOX-1734
Resolves #1713

Documentation

No docs changes needed.

Tests

Executed cpu, disk and memory stress tests locally (using very abbreviated runtimes) to confirm that the commands were provided for each test case. In the case of the disk and memory tests, which run them individually, output looks like this:

$ sudo ./stress_ng_test.py disk -d /dev/sdc -b 1
Using test directory: '/mnt/sdc/tmp/stress-ng-33748cb3-e56f-11ef-a0bc-d8bbc1046e12'
Estimated total run time is 0 minutes

Running command: stress-ng --aggressive --verify --timeout 1 --temp-path /mnt/sdc/tmp/stress-ng-33748cb3-e56f-11ef-a0bc-d8bbc1046e12 --hdd-opts dsync --readahead-bytes 16M -k --aio 0
07 Feb 16:18: Running stress-ng aio stressor for 1 seconds...
stress-ng: info:  [2993691] setting to a 1 secs run per stressor
stress-ng: info:  [2993691] dispatching hogs: 20 aio
stress-ng: info:  [2993691] skipped: 0
stress-ng: info:  [2993691] passed: 19: aio (19)
stress-ng: info:  [2993691] failed: 0
stress-ng: info:  [2993691] metrics untrustworthy: 0
stress-ng: info:  [2993691] successful run completed in 1.05 secs

Running command: stress-ng --aggressive --verify --timeout 1 --temp-path /mnt/sdc/tmp/stress-ng-33748cb3-e56f-11ef-a0bc-d8bbc1046e12 --hdd-opts dsync --readahead-bytes 16M -k --aiol 0
07 Feb 16:18: Running stress-ng aiol stressor for 1 seconds...
stress-ng: info:  [2993761] setting to a 1 secs run per stressor
stress-ng: info:  [2993761] dispatching hogs: 20 aiol
stress-ng: info:  [2993761] skipped: 0
stress-ng: info:  [2993761] passed: 19: aiol (19)
stress-ng: info:  [2993761] failed: 0
stress-ng: info:  [2993761] metrics untrustworthy: 0
stress-ng: info:  [2993761] successful run completed in 1.08 secs

and for CPU:
`
$ sudo ./stress_ng_test.py cpu -b 1
Estimated total run time is 0 minutes

Running command: stress-ng --aggressive --verify --timeout 1 --metrics-brief --tz --times --af-alg 0 --bsearch 0 --context 0 --cpu 0 --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 --matrix 0 --qsort 0 --str 0 --stream 0 --tsearch 0 --vecmath 0 --wcs 0
07 Feb 17:15: Running multiple stress-ng stressors in parallel for 1
seconds...
`

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 48.44%. Comparing base (6205aed) to head (94695e8).
Report is 205 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1714      +/-   ##
==========================================
+ Coverage   48.32%   48.44%   +0.11%     
==========================================
  Files         372      368       -4     
  Lines       40091    39881     -210     
  Branches     6759     6739      -20     
==========================================
- Hits        19373    19319      -54     
+ Misses      20002    19847     -155     
+ Partials      716      715       -1     

Flag	Coverage Δ
provider-base	24.80% <100.00%> (∅)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.