hw_vars: remove the default 300s runtime setting

It could be a surprise for people to find their test cases that doesn't
specify runtime in cmdline to have their run stopped prematurely and
only find the runtime is set in hw_vars.

Tests that have a need to be stopped at 300s should set the runtime
environment variable, unconditionally timeout after 300s in hw_vars
doesn't seem appropriate.

Signed-off-by: Aaron Lu <aaron.lu@intel.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>

1 files changed, 5 insertions, 3 deletions

diff --git a/hw_vars b/hw_vars
index 4f8c5d3..d47592f 100755
--- a/hw_vars
+++ b/hw_vars
@@ -1,8 +1,10 @@
 #!/bin/sh
 
-[ -n "$runtime" ] || runtime=300
-
-USEMEM="$CMD ./usemem --runtime $runtime"
+if [ -n "$runtime" ]; then
+	USEMEM="$CMD ./usemem --runtime $runtime"
+else
+	USEMEM="$CMD ./usemem"
+fi
 
 TMPFS_MNT=/tmp/vm-scalability-tmp
 SHM_FILE=$TMPFS_MNT/sparse-${0#*case-}