Eliminate Pester duplicate failures in Problems view. #941
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
When tasks is set to 2.0.0, the tasks run in the terminal and in this case, Pester outputs a bunch of progress text to the terminal. This results in duplicate failures being found by the problem matcher. Work around this problem for now by eliminating the Pester progress output. For more details see - microsoft/vscode#22065 (comment)
|
Note: we still have a problem if the terminal window is too narrow. PowerShell will wrap the line that contains the line number and file path. The current $pester problem matcher expects this info to be on a single line. I'll look into updating the problem matcher but that might not be so easy. Workaround for now is to make your terminal window wider (or use tasks 0.1.0). |
|
Cool, thanks! |
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 tasks is set to 2.0.0, the tasks run in the terminal and in this case, Pester outputs a bunch of progress text to the terminal. This results in duplicate failures being found by the problem matcher.
Work around this problem for now by eliminating the Pester progress output. For more details see - microsoft/vscode#22065 (comment)