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

Re: [PATCH v4 1/4] add function test_must_fail_or_sigpipe and use it to fix flaky tests

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 6, 2015, 18:49 UTC
Message-ID
<xmqqmvur2cb8.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<xmqqr3k32dc9.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 5 quoted lines
> Adding the third variant in the way this patch does is making things
> worse by inviting more mistakes.
>
> How about doing something like the attached to consolidate the
> existing two into one, and then build this third one on top?

Actually, I think this other variant I came up with is cleaner and is more easily extensible. It already has the support for sigpipe, e.g. you can do

	test_must_fail ok=sigpipe git fetch ...
Of course, you can do
	test_must_fail_or_sigpipe () {
		test_must_fail ok=sigpipe "$@"
	}

if it is easier to read. I do not have a very strong opinion either way.

 t/test-lib-functions.sh | 28 +++++++++++++++++-----------
 1 file changed, 17 insertions(+), 11 deletions(-)
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index e8d3c0f..b732f87 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -560,11 +560,26 @@ test_line_count () {
 # the failure could be due to a segv.  We want a controlled failure.
 
 test_must_fail () {
+	case "$1" in
+	ok=*)
+		_test_ok=${1#ok=}
+		shift
+		;;
+	*)
+		_test_ok=
+		;;
+	esac
 	"$@"
 	exit_code=$?
-	if test $exit_code = 0; then
+	if ! case ",$_test_ok," in *,success,*) false;; esac &&
+	   test $exit_code = 0
+	then
 		echo >&2 "test_must_fail: command succeeded: $*"
 		return 1
+	elif ! case ",$_test_ok," in *,sigpipe,*) false;; esac &&
+	   test $exit_code = 141
+	then
+		return 0
 	elif test $exit_code -gt 129 && test $exit_code -le 192; then
 		echo >&2 "test_must_fail: died by signal: $*"
 		return 1
@@ -590,16 +605,7 @@ test_must_fail () {
 # because we want to notice if it fails due to segv.
 
 test_might_fail () {
-	"$@"
-	exit_code=$?
-	if test $exit_code -gt 129 && test $exit_code -le 192; then
-		echo >&2 "test_might_fail: died by signal: $*"
-		return 1
-	elif test $exit_code = 127; then
-		echo >&2 "test_might_fail: command not found: $*"
-		return 1
-	fi
-	return 0
+	test_must_fail ok=success "$@"
 }
 
 # Similar to test_must_fail and test_might_fail, but check that a
Previous: Junio C HamanoNext: larsxschneider@gmail.com
Message 4 of 20 in “Add Travis CI support”
  1. 0/4 Add Travis CI supportlarsxschneider@gmail.com, Nov 6, 2015
  2. 1/4 add function test_must_fail_or_sigpipe and use it to fix flaky testslarsxschneider@gmail.com, Nov 6, 2015
  3. Junio C HamanoNov 6, 2015
  4. Junio C HamanoNov 6, 2015
  5. 2/4 git-p4: add p4d timeout in testslarsxschneider@gmail.com, Nov 6, 2015
  6. Eric SunshineNov 6, 2015
  7. Lars SchneiderNov 6, 2015
  8. 3/4 git-p4: retry kill/cleanup operations in tests with timeoutlarsxschneider@gmail.com, Nov 6, 2015
  9. Eric SunshineNov 6, 2015
  10. Lars SchneiderNov 6, 2015
  11. Lars SchneiderNov 6, 2015
  12. 4/4 Add Travis CI supportlarsxschneider@gmail.com, Nov 6, 2015
  13. Eric SunshineNov 6, 2015
  14. Lars SchneiderNov 6, 2015
  15. Sebastian SchuberthNov 6, 2015
  16. Lars SchneiderNov 6, 2015
  17. Sebastian SchuberthNov 6, 2015
  18. Lars SchneiderNov 6, 2015
  19. Sebastian SchuberthNov 6, 2015
  20. Lars SchneiderNov 6, 2015

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.