On 4/21/23 08:05, Daniel Wagner wrote:
The fio jobs are supposed to run long in background during the test.
Instead relying on a job size use explicit runtime for this.
Signed-off-by: Daniel Wagner <dwagner@xxxxxxx>
---
tests/nvme/032 | 2 +-
tests/nvme/040 | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/tests/nvme/032 b/tests/nvme/032
index 017d4a339971..81e074cc11bc 100755
--- a/tests/nvme/032
+++ b/tests/nvme/032
@@ -39,7 +39,7 @@ test_device() {
# start fio job
_run_fio_rand_io --filename="$TEST_DEV" --size=1g \
- --group_reporting &> /dev/null &
+ --group_reporting --time_based --runtime=1m &> /dev/null &
sleep 5
diff --git a/tests/nvme/040 b/tests/nvme/040
index 04bd726cd309..8d29f905adb5 100755
--- a/tests/nvme/040
+++ b/tests/nvme/040
@@ -38,7 +38,8 @@ test() {
# start fio job
echo "starting background fio"
_run_fio_rand_io --filename="/dev/${nvmedev}n1" --size=1g \
- --group_reporting --ramp_time=5 &> /dev/null &
+ --group_reporting --ramp_time=5 \
+ --time_based --runtime=1m &> /dev/null &
sleep 5
# do reset/remove operation
Wouldn't it be better to let _run_fio_rand_io pick the correct size?
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@xxxxxxx +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman
