aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJon Turney <jon.turney@dronecode.org.uk>2017-10-27 14:39:10 +0100
committerJon Turney <jon.turney@dronecode.org.uk>2018-02-15 12:51:24 +0000
commit2a64ed855e6db81c3df4659e1066f777b9bacc8c (patch)
tree2231b7f6571b017a475adf527cc46f8f01ebde7b /docs
parent9dc995b3e92a029fb1e563d1ca19365ac5fec804 (diff)
downloadmeson-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 'docs')
-rw-r--r--docs/markdown/Running-Meson.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/markdown/Running-Meson.md b/docs/markdown/Running-Meson.md
index 23d5e97..14b2d19 100644
--- a/docs/markdown/Running-Meson.md
+++ b/docs/markdown/Running-Meson.md
@@ -146,3 +146,9 @@ Meson has a standard command line help feature. It can be accessed
with the following command.
meson --help
+
+Exit status
+==
+
+Meson exits with status 0 if successful, 1 for problems with the command line or
+meson.build file, and 2 for internal errors.