add -d, --debug option to pipe the test's stderr #15
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
|
Isaac, there is also a similar pull request in issue 31 - #31 In my version, I did not make stderr optional, it always forwards stderr (if TAP and TAP_DIAG are both not set). I did add a test to verify the output if you want to adapt it for this patch. Whatever you prefer. |
isaacs
pushed a commit
that referenced
this pull request
Sep 1, 2023
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
resolves this issue: #3
I've only supported piping stderr, because that is where debugging output should go.
Maybe people will still want to show stdout, but then you would have to filter out what tap-consumer did not parse.
And that isn't coming in on this sunday morning pull request.