travis: don't run the tests before the sonar analysis

We exeed the 40mn timeframe on travis with those tests.
Too bad, we gonna lose the coverage information...

diff --git a/tools/internal/travis-sonarqube.sh b/tools/internal/travis-sonarqube.sh
index 84a581c..98411ef 100755 (executable)
--- a/tools/internal/travis-sonarqube.sh
+++ b/tools/internal/travis-sonarqube.sh
@@ -32,10 +32,12 @@ installBuildWrapper
 ./build-wrapper-linux-x86/build-wrapper-linux-x86-64 --out-dir bw-outputs "$@"
 
 # Run ctest before sonar to gather coverage some information
-set +e
-ctest -j4 --output-on-failure
-outcome=$?
-set -e
+# EDIT: Don't run the tests on travis because they take too much time.
+#set +e
+#ctest -j4 --output-on-failure
+#outcome=$?
+#set -e
+outcome=0
 
 # Only run sonar on master (not on pull requests)
 if [ "$TRAVIS_PULL_REQUEST" != "false" ] ; then
@@ -43,7 +45,7 @@ if [ "$TRAVIS_PULL_REQUEST" != "false" ] ; then
 fi
 
 # generate the gcov files
-ctest -D ExperimentalCoverage
+#ctest -D ExperimentalCoverage
 
 # and finally execute the actual SonarQube analysis
 # (the SONAR_TOKEN is set from the travis web interface, to not expose it with an ongoing "set -x")