Properly write error/failure log to stderr #570
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* log.ok -> stdin * log.error -> stderr* * log.success -> stdin * log.fail -> stderr*
|
hmm, need to fix the testcases |
|
We're not going to change the stdout/sterr behavior for 0.4, but are looking into it for 0.5. |
|
Shall I open a new PR or a new issue? |
|
It's already in the 0.5 planning wiki, thanks! |
|
Hi We run Grunt thru an ant task and we've been hit by this stderr bug, ant won't fail when grunt fails. Has this feature landed on master yet ? Ty |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New PR based on #511 (well and #512), but now back on top of master branch.