test_runner: display coverage errors in dot reporter#64695
Open
elephant-y wants to merge 1 commit into
Open
Conversation
Collaborator
|
Review requested:
|
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.
When using the dot reporter with
--experimental-test-coverageandcoverage thresholds, if a threshold is not met, the dot reporter
outputs only dots (
.) with no error message. The process exits withcode 1 but gives no indication of what went wrong.
This happens because the dot reporter does not handle
test:diagnosticevents witherrorlevel, which are emitted whencoverage thresholds are not satisfied.
Changes
test:diagnosticevents withlevel === 'error'similar to how failed tests are displayed
Before
After
Fixes: #60884