Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Git HEAD] make check keeps exiting with code 0 despite failures #348

Closed
hartwork opened this issue Dec 18, 2024 · 5 comments
Closed

[Git HEAD] make check keeps exiting with code 0 despite failures #348

hartwork opened this issue Dec 18, 2024 · 5 comments

Comments

@hartwork
Copy link
Contributor

Hi!

make check keeps exiting with code 0 despite failures which is unfortunate in context of CI and/or distro packaging. It would be great to exit with code 1 in case of (errors and/or) failures. Thank you!

Best, Sebastian

henry2cox added a commit that referenced this issue Dec 19, 2024
GitHub regression fixes. #343, #348

Signed-off-by: Henry Cox <[email protected]>
@hartwork
Copy link
Contributor Author

@henry2cox commit 193cc76 made the CI rely on make check exiting with non-zero code in case of test failures a few hours ago. Was there some other commit that made make check do that or will the CI now just be green even not all tests were successful? That would defeat it's key mission, so I'm wondering. What do you think?

@henry2cox
Copy link
Collaborator

Sorry - not trying to confuse things (...but succeeding remarkably effectively) - the fix for exit status is line 161 in the test_run script - which I checked in with the other fixes, in 193cc76.
It should be doing what we want: if tests all pass: zero exit status. If something breaks: nonzero.

@hartwork
Copy link
Contributor Author

@henry2cox cool! So we can close this as fixed and keep the CI calling make check as is?

@hartwork
Copy link
Contributor Author

@henry2cox update: Found your message #343 (comment) now — closing as fixed…

@henry2cox
Copy link
Collaborator

I think so - yes.
And, in the meantime, we can see if we can make the artifact job more useful/usable - and more paranoid.
(Paranoia in regression/release testing is a Good Thing, IMO.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants