Skip to content
This repository has been archived by the owner on Oct 4, 2023. It is now read-only.

Exit status and stdout / stderr problems #81

Open
troessner opened this issue Jun 15, 2015 · 1 comment
Open

Exit status and stdout / stderr problems #81

troessner opened this issue Jun 15, 2015 · 1 comment

Comments

@troessner
Copy link

We'd love to integrate ataru into our CI process but we're kind of blocked from doing this because of two reasons:

1.) ataru does not set any exit status depending on what the check actually resulted in.
Meaning that this

 echo $?
0

will always be the same. Which makes it not suitable for CI integration since there's no automated way of knowing when the checks failed.

2.) When something goes wrong, e.g. a syntax error in the source code ataru still prints on STDOUT. Not on STDERR. So there is no way of telling the difference between output that one can ignore and legitimate failures.

Am I missing something here or is [1] and [2] something we just have to live with?

P.S.: Discussion started initally here: troessner/reek#540

@troessner
Copy link
Author

Update: [1] was my bad because of the way we shelled out to ataru in the rake task, please ignore that.
I'd still be interested in [2] though..;)

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

No branches or pull requests

1 participant