-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Description:
When untarring the results_iozone_throughput-performance.tar left behind after a run, the contents are spread out in the current directory. Compare with other tests such as fio which keep each run's output in a timestamped subdirectory allowing multiple runs' output to coexist.
Current behavior:
iozone results end up in $rundir
tar tvf results_iozone_throughput-performance.tar
-rw-r--r-- root/root 10788 2024-09-26 12:12 build-run.log
drwxr-xr-x root/root 0 2024-09-26 12:06 config/
-r--r--r-- root/root 231202 2024-09-26 12:06 config/cpuinfo
-rw-r--r-- root/root 190262 2024-09-26 12:06 config/dmesg
-rw-r--r-- root/root 22844 2024-09-26 12:06 config/NUMAlayout
drwxr-xr-x root/root 0 2024-09-26 12:06 data/
-rw-r--r-- root/root 441 2024-09-26 12:12 results.csv
drwxr-xr-x root/root 0 2024-09-26 12:06 Run_1/
drwxr-xr-x root/root 0 2024-09-26 12:07 Run_1/xfs/
-rw-r--r-- root/root 15300 2024-09-26 12:12 Run_1/xfs/<broken_filename_already_logged>
-rw-r--r-- root/root 4 2024-09-26 12:12 test_results_report
Desired behavior:
iozone results end up in a timestamped subdirectory
tar tvf results_iozone_throughput-performance.tar
drwxr-xr-x root/root 0 2024-09-26 12:06 iozone-2024.09.06-11.18.24/
and the rest goes under that