Merged
Conversation
The TAP 13 spec [1] states that the trailing delimiter for yaml diagnostics is "\s+...\n", not "\s+---\n". This causes prove to fail to parse the output of git's unit tests when they fail. NB If we ever want to change to using TAP 14 then we'll need to change the indentation as it requires a strict two space indentation. [1] https://testanything.org/tap-version-13-specification.html Reported-by: Jeff King <[email protected]>
Member
|
Indeed. Quoting the relevant part from the spec:
So yes, this is an obvious fix. Thanks! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The TAP 13 spec [1] states that the trailing delimiter for yaml diagnostics is "\s+...\n", not "\s+---\n". This causes prove to fail to parse the output of git's unit tests when they fail.
[1] https://testanything.org/tap-version-13-specification.html