diff options
| author | Jon Turney <jon.turney@dronecode.org.uk> | 2017-10-27 14:39:10 +0100 |
|---|---|---|
| committer | Jon Turney <jon.turney@dronecode.org.uk> | 2018-02-15 12:51:24 +0000 |
| commit | 2a64ed855e6db81c3df4659e1066f777b9bacc8c (patch) | |
| tree | 2231b7f6571b017a475adf527cc46f8f01ebde7b /man | |
| parent | 9dc995b3e92a029fb1e563d1ca19365ac5fec804 (diff) | |
| download | meson-2a64ed855e6db81c3df4659e1066f777b9bacc8c.zip meson-2a64ed855e6db81c3df4659e1066f777b9bacc8c.tar.gz meson-2a64ed855e6db81c3df4659e1066f777b9bacc8c.tar.bz2 | |
Verify that failing tests are failing with an error, not a python exception
PR #2527 suggests "making failing tests more strict about failing
gracefully".
To achive this, make meson exit with distinct exit statuses for meson errors
and python exceptions, and check the exit status is as expected for failing
tests.
I can't see how to write a test for this, within the current framework.
You can test this change by reverting the fix (but not the test) from commit
1a159db8 and verifying that 'test cases/failing/66 string as link target'
fails.
Diffstat (limited to 'man')
| -rw-r--r-- | man/meson.1 | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/man/meson.1 b/man/meson.1 index 929bc6e..4429fa2 100644 --- a/man/meson.1 +++ b/man/meson.1 @@ -202,6 +202,19 @@ show available versions of the specified project \fBstatus\fR show installed and available versions of currently used subprojects +.SH EXIT STATUS + +.TP +.B 0 +Successful. +.TP +.B 1 +Usage error, or an error parsing or executing meson.build. +.TP +.B 2 +Internal error. +.TP + .SH SEE ALSO http://mesonbuild.com/ |