Stabilize parallel Pester smoke discovery - #717
Merged
Conversation
Pester can corrupt discovery state when concurrent ThreadJobs share the parent host. Replay buffered output after each job completes instead.
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.
Summary
Cause
Master smoke run 34568913568 exposed a sporadic Pester 5.9.1 discovery failure while concurrent ThreadJobs shared the parent host. The following master run passed on the same tree, confirming a race rather than a Jira API regression.
This follows the workaround documented in pester/Pester#2383 while preserving throttling, per-file timeouts, result aggregation, and useful CI output.
Validation
Release intent
Test infrastructure only. No package release.