env CAPTURE_STDERR=false lets devs see hard failures #1178
Merged
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
|
@jfelchner :) |
|
👍 😀 |
|
👍 |
NullVoxPopuli
added a commit
that referenced
this pull request
Sep 18, 2015
env CAPTURE_STDERR=false lets devs see hard failures
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.
I noticed that if I had runtime errors, I wouldn't see the stacktrace
or exception message.
Turns out, this is something about the at_exit resolution of io
capturing between capture_errors and Minitest.
I couldn't figure out how to modify the io for Minitest without a lot of
code, so this is a safety valve for devs :) :(
MiniTest 4
Minitest 5