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

Re: [PATCH] Do not ignore errors during make check

From
Junio C Hamano <junkio@cox.net>
Date
Dec 14, 2005, 21:30 UTC
Message-ID
<7v1x0fxt7b.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20051214210932.GA2642@kvasir.watson.ibm.com>
Amos Waterland <apw@us.ibm.com> writes:
Show 5 quoted lines
> Do not let errors pass by unnoticed when running `make check'.
> ...
>  check:
> -	for i in *.c; do sparse $(ALL_CFLAGS) $(SPARSE_FLAGS) $$i; done
> +	for i in *.c; do sparse $(ALL_CFLAGS) $(SPARSE_FLAGS) $$i || break; done

Good point but "|| exit" would be more appropriate. With the above patch, I suspect "make check" merely stops at the first error but resulting return code would still be zero, wouldn't it?

$ cat Makefile
check1:
	for i in 1 2 3 4; do echo testing $$i; test $$i -le 2 || break; done
check2:
	for i in 1 2 3 4; do echo testing $$i; test $$i -le 2 || exit; done
$ make check1
for i in 1 2 3 4; do echo testing $i; test $i -le 2 || break; done
testing 1
testing 2
testing 3
$ make check2
for i in 1 2 3 4; do echo testing $i; test $i -le 2 || exit; done
testing 1
testing 2
testing 3
make: *** [check2] Error 1
$ exit
Previous: Amos WaterlandNext: Amos Waterland
Message 2 of 4 in “Do not ignore errors during make check”
  1. Do not ignore errors during make checkAmos Waterland, Dec 14, 2005
  2. Junio C HamanoDec 14, 2005
  3. Amos WaterlandDec 14, 2005
  4. Linus TorvaldsDec 14, 2005

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.