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

Exit status code should not be 0 on error #13

Closed
OndraM opened this issue May 20, 2015 · 0 comments
Closed

Exit status code should not be 0 on error #13

OndraM opened this issue May 20, 2015 · 0 comments

Comments

@OndraM
Copy link
Member

OndraM commented May 20, 2015

When error occurs in any test, the Steward exit code should not be 0.

For example on Travis CI in our https://github.com/lmc-eu/steward-example - if you don't read logs, you won't find that some test is failing.

On the other side - as the test tends to be unstable on some circumstances, and this "non-zero" exit code of the process would fail whole build eg. on Jenkins, this may not be completely needed behavior, because even with failing test you want the build to "succeed", so Jenkins would log its history, process JUnit graphs etc.

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

1 participant