You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently meson has no way to assert that a test returns an exact exit code, this would be useful if a test is expected to fail with a specific failure state. it would also allow tests that should_fail to distinguish between an error code and a segmentation fault or abort. Would this be something meson would be open to allowing or is there a specific reason why this isnt implemented?
The text was updated successfully, but these errors were encountered:
The problem with should_fail is that it doesn't indicate that the test passes if the exit code indicates failure... rather, should_fail indicates that the test is supposed to be an "expected failure", i.e. a known bug (and if it ever emits a successful exit code, the test runner should report an "unexpected pass" which you're supposed to fix by removing the should_fail keyword).
Currently meson has no way to assert that a test returns an exact exit code, this would be useful if a test is expected to fail with a specific failure state. it would also allow tests that
should_fail
to distinguish between an error code and a segmentation fault or abort. Would this be something meson would be open to allowing or is there a specific reason why this isnt implemented?The text was updated successfully, but these errors were encountered: