From f24f2c6b154e9749efb94d931fff80905e20549a Mon Sep 17 00:00:00 2001 From: Bryce Kwon Date: Sat, 7 Nov 2026 08:50:51 -1000 Subject: Name the build a test run is testing After tools/build-development.sh or build-release.sh, a plain make test quietly rebuilt without the sanitizers or the hardening and tested that binary instead, with nothing in its output to say so. --- tests/Makefile | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/tests/Makefile b/tests/Makefile index a693e92..9a78c42 100644 --- a/tests/Makefile +++ b/tests/Makefile @@ -23,9 +23,15 @@ TESTS = $(sort $(wildcard t[0-9][0-9][0-9][0-9]-*.sh)) # A failing script would stop make and leave every later one unrun, so the # scripts run in a make of their own that keeps going, and the summary fails -# the run once all of them have had their turn. +# the run once all of them have had their turn. make test rebuilds with the +# flags on its own command line, so the run first names the compiler and the +# flags the build used, which Git records ahead of its own -I., and any +# sanitizers, which it adds after. .PHONY: all all: + @sed -e 's/ -I\. .* \(-fsanitize=[^ ]*\) .*/ \1/' -e 's/ -I\. .*//' \ + -e 's/^\([^:]*\): */testing cgit as built by \1 with /' \ + ../vendor/git/GIT-CFLAGS @$(MAKE) -k $(TESTS) || : @'$(SHELL_PATH_SQ)' aggregate-results.sh $(TESTS) -- cgit 2.12.1