ci: Stop if valgrind detects errors

* In CI all tests failed to run under valgrind since we compiled with
  ASAN
* Tests should be compiled with ASAN/UBSAN unless they are being run
  under valgrind.
* The way the tests were run meant that failing tests didn't fail the
  overall CI job.

Author: NickeZ

.ci/ci

@@ -20,13 +20,20 @@ make -C py
 ./.ci/check-release-sigs
 
 # Make build directories so we can do some static analysis
+#  - prepare-tidy will create build dirs and more importantly the
+#    compile_commands.json needed for clang-tidy
 make prepare-tidy
 ./.ci/check-tidy
 
 # Build and run Unit tests
-make -j8 unit-test SANITIZE=OFF
+make -j8 unit-test
 make -j8 run-unit-tests
 make -j8 run-rust-unit-tests
+
+# Delete the build directories so that SANITIZE=OFF will take effect
+# Valgrind cannot run programs compiled with address sanitizing on.
+make clean
+make -j8 unit-test SANITIZE=OFF
 make -j8 run-valgrind-on-unit-tests
 
 # BUild simulator

Makefile

@@ -105,7 +105,7 @@ coverage: | build-build
 #./build/bin/test_ui_component_gestures;
 run-valgrind-on-unit-tests:
 	$(MAKE) unit-test
-	bash -c 'find build-build/bin/ -name "test_*" -exec valgrind --leak-check=yes --track-origins=yes {} \;'
+	bash -ec 'for exe in build-build/bin/test_*; do  valgrind --leak-check=yes --track-origins=yes --error-exitcode=1 --exit-on-first-error=yes $$exe; done'
 flash-dev-firmware:
 	./py/load_firmware.py build/bin/firmware.bin --debug
 jlink-flash-bootloader-development: | build