The test suite often fails because of unclean environments where
stale LTTng processes are left running. Since the test suite
assumes that no LTTng process (daemons and test applications) are
running, it makes sense to force the user to kill all those
processes before running the test suite.
The warn_processes.sh script now prints an error and returns 1
to indicate an early failure to the test harness.
It is possible to circumvent this check by invoking the tests
manually or by removing the "exit 1" from the warn_processes.sh
script if there is a need to have persistent processes across
the execution of the test suite.
Signed-off-by: Jonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
exit
fi
-color_warn='\E[1;33m'
+color_error='\E[1;91m'
color_reset='\E[0m'
color_bold='\E[1m'
if [ $? -eq 0 ]; then
pids="$(cut -d ' ' -f 1 <<< "$lttng_processes" | tr '\n' ' ')"
- echo -e "${color_warn}Warning: the following LTTng processes were detected running on the system:$color_reset"
+ echo -e "${color_error}Error: the following LTTng processes were detected running on the system:$color_reset"
echo
echo "$lttng_processes"
echo
echo -e "Here's how to kill them: ${color_bold}kill -9 $pids$color_reset"
- echo -e "${color_warn}If you leave them alive, some tests could fail.$color_reset"
echo
+ echo "The test suite will not run in the presence of those processes since its result may not be reliable."
+ echo
+ exit 1
fi