From 30f343e8c327068778180dbda49edf5453067ec6 Mon Sep 17 00:00:00 2001
From: Olev Kartau <olev.kartau@intel.com>
Date: Fri, 10 Nov 2017 13:44:30 +0200
Subject: [PATCH] CI tester-exec.sh: use explicit test plan name in daft call

This reduces risk that some other test plan gets used.

Signed-off-by: Olev Kartau <olev.kartau@intel.com>
---
 docker/tester-exec.sh | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docker/tester-exec.sh b/docker/tester-exec.sh
index 3cd87bf280..7491610b41 100755
--- a/docker/tester-exec.sh
+++ b/docker/tester-exec.sh
@@ -110,12 +110,13 @@ testimg() {
     cp $HOME/.config.ini.wlan ${_WLANCONF}
     chmod 644 ${_WLANCONF}
 
-    daft ${DEVICE} ${FILENAME} --record
+    _daft_args="${DEVICE} ${FILENAME} --record --testplan iot_qatest"
+    daft $_daft_args
     TEST_EXIT_CODE=$?
     if [ "$TEST_EXIT_CODE" = 1 ]; then
       echo "WARNING: daft=1 would lead to UNSTABLE: wipe results, retry daft"
       rm -f *.log *.log.raw *.xml
-      daft ${DEVICE} ${FILENAME} --record
+      daft $_daft_args
       TEST_EXIT_CODE=$?
     fi
   fi