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

[RFC PATCH] tests: print failed test numbers at the end of the test run

From
Jens Lehmann <jens.lehmann@web.de>
Date
Jul 23, 2011, 19:16 UTC
Message-ID
<4E2B1DF2.4000003@web.de>

On modern multi-core processors "make test" is often run in multiple jobs. If one of them fails the test run does stop, but the concurrently running tests finish their run. Finding out what test is broken involves a lot of scrolling. That gets even worse when the -i option is used.

If one or more tests failed, print a list of them before the test summary:
failed test(s): t1000 t6500

fixed 0 success 7638 failed 3 broken 49 total 7723

This makes it possible to just run the test suite with -i and collect all failed test scripts at the end for further examination.

Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
---

Maybe I'm missing something completely obvious, but I always have a hard time finding out which test scripts did fail in a test run with -j30.

 t/aggregate-results.sh |   12 +++++++++++-
 1 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/t/aggregate-results.sh b/t/aggregate-results.sh
index d206b7c..b8e929a 100755
--- a/t/aggregate-results.sh
+++ b/t/aggregate-results.sh
@@ -1,5 +1,6 @@
 #!/bin/sh

+failed_tests=
 fixed=0
 success=0
 failed=0
@@ -18,7 +19,12 @@ do
 		success)
 			success=$(($success + $value)) ;;
 		failed)
-			failed=$(($failed + $value)) ;;
+			failed=$(($failed + $value))
+			if test $value != 0; then
+				testnum=$(echo $file | cut -b 14-18)
+				failed_tests="$failed_tests $testnum"
+			fi
+			;;
 		broken)
 			broken=$(($broken + $value)) ;;
 		total)
@@ -27,6 +33,10 @@ do
 	done <"$file"
 done

+if [ -n "$failed_tests" ]; then
+	printf "\nfailed test(s):$failed_tests\n\n"
+fi
+
 printf "%-8s%d\n" fixed $fixed
 printf "%-8s%d\n" success $success
 printf "%-8s%d\n" failed $failed
-- 
1.7.6.346.g750efc
Next: Junio C Hamano
Message 1 of 9 in “tests: print failed test numbers at the end of the test run”
  1. tests: print failed test numbers at the end of the test runJens Lehmann, Jul 23, 2011
  2. Junio C HamanoJul 24, 2011
  3. tests: print failed test numbers at the end of the test runJens Lehmann, Jul 24, 2011
  4. Jeff KingJul 24, 2011
  5. Jens LehmannJul 24, 2011
  6. Sverre RabbelierJul 25, 2011
  7. Nguyen Thai Ngoc DuyJul 26, 2011
  8. Jeff KingJul 26, 2011
  9. Jeff KingJul 26, 2011

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.