diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-08-27 12:34:02 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-08-27 12:34:02 -0400 |
| commit | b26ee162f33858aa4ef82fbe3d56eecc00590755 (patch) | |
| tree | 61948b08f7dd069f972e40faabd24102ea438549 /doc | |
| parent | 6e750764b7d30d9cb0684cdaadd79ec091a4fda6 (diff) | |
guess not everyone configures their shell to show nonzero exit codes..
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn b/doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn index 7a579f8fe..2f486ad65 100644 --- a/doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn +++ b/doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn @@ -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]] |