From 190ab2755e9a97b25052590dbc7fce54cd67d355 Mon Sep 17 00:00:00 2001
From: Marco Capetta <mcapetta@sipwise.com>
Date: Fri, 13 Dec 2019 11:48:45 +0100
Subject: [PATCH] TT#71552 Continue bin/check.sh execution in case of sipp
 errors

In case of sipp errors bin/check.sh was aborted without moving
the scenario_ids.yml, moving the json files and cleaning the
scenario's data if required.

Change-Id: Ibb1b5c1874476ff2f483488670f8c3953c38c58f
---
 bin/check.sh | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/bin/check.sh b/bin/check.sh
index b584124b..2b745933 100755
--- a/bin/check.sh
+++ b/bin/check.sh
@@ -32,6 +32,7 @@ GRAPH_FAIL=false
 JSON_KAM=true
 SKIP_MOVE_JSON_KAM=false
 CDR=false
+ERR_FLAG=0
 
 
 # sipwise password for mysql connections
@@ -574,7 +575,8 @@ run_sipp() {
   fi
 
   if [[ ${status} -ne 0 ]]; then
-    error_helper "error in sipp" 2
+    echo "error in sipp!"
+    ERR_FLAG=1;
   fi
 }
 
@@ -854,7 +856,6 @@ fi
 
 
 # let's check the results
-ERR_FLAG=0
 if ! "${SKIP_TESTS}" ; then
   echo "$(date) - ================================================================================="
   echo "$(date) - Check [${GROUP}/${PROFILE}]: ${NAME_CHECK}"