fix: keep GitHub annotations parseable with dot reporter#41292
Open
mturac wants to merge 1 commit into
Open
Conversation
Author
@microsoft-github-policy-service agree |
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
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.
Fixes #41272.
Summary
This keeps GitHub failure annotations parseable when the GitHub reporter is combined with reporters that leave output on the current line, such as the dot reporter.
The fix emits a line break before per-test GitHub failure annotations, so the
::errorworkflow command starts at the beginning of a line. It also adds a regression forreporter: "dot,github"to ensure the annotation is not written inline after the dot reporter output.Validation
npm run ttest -- reporter-github.spec.tsnpx eslint packages/playwright/src/reporters/github.ts tests/playwright-test/reporter-github.spec.tsnpm run tsc -- --pretty falsenpm run buildgit diff --check