diff options
| author |  http://peter-simons.myopenid.com/ <http://peter-simons.myopenid.com/@web> | 2011-08-26 10:55:43 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-08-26 10:55:43 +0000 |
| commit | 9170e1b87d1eac000e9ea4d3944a73209ba9c718 (patch) | |
| tree | 494f74aaf12129145fed9b7af8c5d652752253e2 | |
| parent | 20259c2955e408a72e0960207fc8be4cbeec2e21 (diff) | |
| -rw-r--r-- | doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn | 1 |
1 files changed, 1 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 new file mode 100644 index 000000000..7a579f8fe --- /dev/null +++ b/doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn @@ -0,0 +1 @@ +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. |