guess not everyone configures their shell to show nonzero exit codes..
This commit is contained in:
parent
6e750764b7
commit
b26ee162f3
2 changed files with 5 additions and 1 deletions
4
Makefile
4
Makefile
|
@ -53,7 +53,9 @@ test: $(bins)
|
|||
@if ! $(GHCMAKE) -O0 test; then \
|
||||
echo "** not running test suite" >&2; \
|
||||
else \
|
||||
./test; \
|
||||
if ! ./test; then \
|
||||
echo "** test suite failed!" >&2; \
|
||||
fi; \
|
||||
fi
|
||||
|
||||
testcoverage: $(bins)
|
||||
|
|
|
@ -1 +1,3 @@
|
|||
When the test suite cannot be compiled, the build just fails silenty. This means that in automated builds there is no easy way to ensure that the generated binaries have passed the test suite, because it may not even have been run! IMHO, "make test" should fail (i.e. return a non-zero exit code) when it can't succeeed.
|
||||
|
||||
> Ok, fixed. --[[Joey]] [[done]]
|
||||
|
|
Loading…
Reference in a new issue