Fix Run.Parallel help, code coverage does not force a sequential run - #2974
Merged
Conversation
The description still listed CodeCoverage among the reasons a parallel run falls back to sequential. That stopped being true when workers started measuring their own file with breakpoints and the parent started merging the hits into one report. Also adds the fallback that was missing, when every file opts out with #pester:no-parallel, which the docs site already lists. about_PesterConfiguration.help.txt is regenerated by build.ps1 -Clean. 🤖
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
1 participant
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
Run.Paralleldescription still listed CodeCoverage among the reasons a parallel run falls back to sequential:That has not been true since workers started measuring their own file with breakpoints and the parent started merging the hits into a single report.
Main.ps1sets$collectCoverageInParallel = $coverageEnabledand never falls back for coverage, and the docs site already documents it correctly.Also adds the fallback that was missing, when every file opts out with
#pester:no-parallel.about_PesterConfiguration.help.txtis regenerated bybuild.ps1 -Clean, so it is in the same commit.test.ps1 -File tst/Help.Tests.ps1 -SkipPTestspasses.Docs side: pester/docs#445 regenerates the configuration table with the same text.
🤖