git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v4 1/2] ci: annotate leaks and stop a leak-sanitizer script at its first failure

From
Harald Nordgren via GitGitGadget <gitgitgadget@gmail.com>
Date
Oct 1, 2026, 18:44 UTC
Message-ID
<138394b48b2422a54fe6862c8701b8869f9dcb4a.1790880255.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.2419.v4.git.git.1790880255.gitgitgadget@gmail.com>
From: Harald Nordgren <haraldnordgren@gmail.com>

A leak is only discovered once, at the end of a whole script, well after every test has already reported ok, and it gets no annotation at all, so a leak-sanitizer job's only visible failure is:

    Process completed with exit code 1.

Give a leak its own annotation. Point it at the test script, the exact line isn't known, only which script the leak turned up in, and put the sanitizer report in a log group next to it, so it stays visible.

Once a script has one leak, it keeps running: the sanitizer log directory is never cleared between tests, so every later test in the same script sees the same leftover log entries and also reports "not ok", burying the one real failure in copies of itself. Stop a leak-sanitizer script at its first failure with --immediate instead.

A failing test already gets its own annotation once its script finishes, but --immediate exits as soon as that test fails, before reaching the code that writes it. Write the annotation first, so turning on --immediate here does not silently drop it.

Signed-off-by: Harald Nordgren <haraldnordgren@gmail.com>
---
 ci/lib.sh                            |  1 +
 t/test-lib-github-workflow-markup.sh | 16 ++++++++++++++++
 t/test-lib.sh                        |  6 +++++-
 3 files changed, 22 insertions(+), 1 deletion(-)
diff --git a/ci/lib.sh b/ci/lib.sh
index c6ccbf8c17..a89f480a78 100755
--- a/ci/lib.sh
+++ b/ci/lib.sh
@@ -382,6 +382,7 @@ linux-leaks|linux-reftable-leaks)
 	export NO_CVS_TESTS=LetsSaveSomeTime
 	export NO_SVN_TESTS=LetsSaveSomeTime
 	export NO_P4_TESTS=LetsSaveSomeTime
+	GIT_TEST_OPTS="$GIT_TEST_OPTS --immediate"
 	;;
 linux-asan-ubsan)
 	export SANITIZE=address,undefined
diff --git a/t/test-lib-github-workflow-markup.sh b/t/test-lib-github-workflow-markup.sh
index fa29a62aa3..0d54496358 100644
--- a/t/test-lib-github-workflow-markup.sh
+++ b/t/test-lib-github-workflow-markup.sh
@@ -28,6 +28,11 @@ start_test_output () {
 	github_markup_output="${GIT_TEST_TEE_OUTPUT_FILE%.out}.markup"
 	>$github_markup_output
 	GIT_TEST_TEE_OFFSET=0
+	github_markup_script_name=${0##*/}
+}
+
+github_annotation_ () {
+	echo >>$github_markup_output "::$1 file=$2,line=$3::$4"
 }
 
 # No need to override start_test_case_output
@@ -53,4 +58,15 @@ finalize_test_case_output () {
 	echo >>$github_markup_output "::endgroup::"
 }
 
+finalize_test_leak_output () {
+	# The exact line the leak turned up on isn't known, only the script,
+	# so point at line 1.
+	github_annotation_ error "t/$github_markup_script_name" 1 \
+		"memory leak logged in $this_test"
+
+	echo >>$github_markup_output "::group::leak: $this_test.$test_count"
+	cat "$TEST_RESULTS_SAN_FILE".* >>$github_markup_output
+	echo >>$github_markup_output "::endgroup::"
+}
+
 # No need to override finalize_test_output
diff --git a/t/test-lib.sh b/t/test-lib.sh
index 1f0505e412..e74a12f1dd 100644
--- a/t/test-lib.sh
+++ b/t/test-lib.sh
@@ -199,6 +199,7 @@ mark_option_requires_arg () {
 start_test_output () { :; }
 start_test_case_output () { :; }
 finalize_test_case_output () { :; }
+finalize_test_leak_output () { :; }
 finalize_test_output () { :; }
 
 parse_option () {
@@ -822,6 +823,9 @@ test_failure_ () {
 	say_color error "not ok $test_count - ${pfx:+$pfx }$1"
 	shift
 	printf '%s\n' "$*" | sed -e 's/^/#	/'
+	# Write the annotation before either --immediate exit path below,
+	# both of which call exit and would otherwise skip it.
+	finalize_test_case_output failure "$failure_label" "$@"
 	if test -n "$immediate"
 	then
 		say_color error "1..$test_count"
@@ -835,7 +839,6 @@ test_failure_ () {
 		check_test_results_san_file_ "$test_failure"
 		_error_exit
 	fi
-	finalize_test_case_output failure "$failure_label" "$@"
 }
 
 test_known_broken_ok_ () {
@@ -1218,6 +1221,7 @@ check_test_results_san_file_ () {
 		return
 	fi &&
 	say_color >&4 error "$(cat "$TEST_RESULTS_SAN_FILE".*)" &&
+	finalize_test_leak_output &&
 
 	if test "$test_failure" = 0
 	then
-- 
gitgitgadget
Previous: Harald Nordgren via GitGitGadgetNext: Harald Nordgren via GitGitGadget
Message 22 of 40 in “ci: point leak-sanitizer failures at the actual test and error”
  1. ci: point leak-sanitizer failures at the actual test and errorHarald Nordgren via GitGitGadget, Sep 25, 2026
  2. Ben KnobleSep 25, 2026
  3. Harald NordgrenSep 25, 2026
  4. Phillip WoodSep 27, 2026
  5. Harald NordgrenSep 27, 2026
  6. 0/2 ci: link failure and leak annotations to the test scriptHarald Nordgren via GitGitGadget, Sep 28, 2026
  7. 2/2 ci: point test failures and fixed known breakages at their file and lineHarald Nordgren via GitGitGadget, Sep 28, 2026
  8. Junio C HamanoSep 28, 2026
  9. 1/2 ci: annotate leaks and stop a leak-sanitizer script at its first failureHarald Nordgren via GitGitGadget, Sep 28, 2026
  10. Junio C HamanoSep 28, 2026
  11. Harald NordgrenSep 29, 2026
  12. 0/2 ci: link failure and leak annotations to the test scriptHarald Nordgren via GitGitGadget, Sep 30, 2026
  13. 1/2 ci: annotate leaks and stop a leak-sanitizer script at its first failureHarald Nordgren via GitGitGadget, Sep 30, 2026
  14. Phillip WoodSep 30, 2026
  15. 2/2 ci: point test failures and fixed known breakages at their file and lineHarald Nordgren via GitGitGadget, Sep 30, 2026
  16. Phillip WoodSep 30, 2026
  17. Harald NordgrenSep 30, 2026
  18. Junio C HamanoSep 30, 2026
  19. Phillip WoodSep 30, 2026
  20. Junio C HamanoSep 30, 2026
  21. 0/2 ci: link failure and leak annotations to the test scriptHarald Nordgren via GitGitGadget, Oct 1, 2026
  22. 1/2 ci: annotate leaks and stop a leak-sanitizer script at its first failureHarald Nordgren via GitGitGadget, Oct 1, 2026
  23. 2/2 ci: point test failures and fixed known breakages at their file and lineHarald Nordgren via GitGitGadget, Oct 1, 2026
  24. Phillip WoodOct 1, 2026
  25. Junio C HamanoOct 1, 2026
  26. Harald NordgrenOct 2, 2026
  27. 0/2 ci: link failure and leak annotations to the test scriptHarald Nordgren via GitGitGadget, Oct 3, 2026
  28. 1/2 ci: annotate leaks and stop a leak-sanitizer script at its first failureHarald Nordgren via GitGitGadget, Oct 3, 2026
  29. 2/2 ci: point test failures and fixed known breakages at their file and lineHarald Nordgren via GitGitGadget, Oct 3, 2026
  30. Phillip WoodOct 3, 2026
  31. Phillip WoodOct 3, 2026
  32. Harald NordgrenOct 4, 2026
  33. Phillip WoodOct 5, 2026
  34. Harald NordgrenOct 5, 2026
  35. Phillip WoodOct 5, 2026
  36. Harald NordgrenOct 4, 2026
  37. 0/2 ci: link failure and leak annotations to the test scriptHarald Nordgren via GitGitGadget, Oct 6, 2026
  38. 1/2 ci: annotate leaks and stop a leak-sanitizer script at its first failureHarald Nordgren via GitGitGadget, Oct 6, 2026
  39. 2/2 ci: point test failures and fixed known breakages at their file and lineHarald Nordgren via GitGitGadget, Oct 6, 2026
  40. Phillip WoodOct 6, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.