[PATCH 11/14] test: Initialise ${TRACE} properly

[David Gibson <david@gibson.dropbear.id.au>]

Unlike ${DEBUG} we don't initialize ${TRACE} to 0 if not set, which cases
failures when testing it later.  That failure acts as though it is false,
however it emits spurious errors in script.log, which can make it harder to
spot real errors.

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
 test/run | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/test/run b/test/run
index e07513f..1945c7b 100755
--- a/test/run
+++ b/test/run
@@ -32,6 +32,9 @@ FAST=${FAST:-1}
 # If set, run passt and pasta with debug options
 DEBUG=${DEBUG:-0}
 
+# If set, run passt and pasta with trace options
+TRACE=${TRACE:-0}
+
 # If set, tell passt and pasta to take packet captures
 PCAP=${PCAP:-0}
 
-- 
@@ -32,6 +32,9 @@ FAST=${FAST:-1}
 # If set, run passt and pasta with debug options
 DEBUG=${DEBUG:-0}
 
+# If set, run passt and pasta with trace options
+TRACE=${TRACE:-0}
+
 # If set, tell passt and pasta to take packet captures
 PCAP=${PCAP:-0}
 
-- 
2.39.2