Update 6.0.0 release notes for parallel data and wall-clock durations#2815
Merged
Conversation
The committed 6.0.0 notes still described the rc1 parallel runner. Fold in
the two user-facing parallel changes made since then:
- Parametrized file containers (New-PesterContainer -Path ... -Data @{...})
now run in parallel, with their -Data handed to each worker, so only
in-memory ScriptBlock containers fall back to the sequential path.
- A parallel run reports its total Duration as wall-clock elapsed time and
leaves the per-phase run totals (user, framework, discovery) blank, since
the files overlap; the per-phase breakdown stays on each container.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The intro reword this commit originally carried was superseded by #2813 on main, which already dropped the release-candidate framing. Keep only the thank-you pluralization, since there were multiple release candidates. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
nohwnd
force-pushed
the
nohwnd-draft-rc3-release
branch
from
c6bf1ef to
463bd66
Compare
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 committed
docs/6.0.0.md(the 6.0.0 final release notes) still described the rc1 parallel runner. This folds in the two user-facing parallel changes made since then so the notes match shipped behavior:New-PesterContainer -Path ... -Data @{...}runs in parallel with its-Datahanded to each worker (Pass data to parallel runs #2803), so the "what falls back" list now correctly names only in-memoryScriptBlockcontainers instead of allContainerinputs.Durationas the orchestrator's measured elapsed time and leaves the per-phase run totals (user, framework, discovery) blank, since the files overlap; the per-phase breakdown stays on each container (Fix parallel run total durations #2807).Docs-only change. The previously merged 7.4+ claim (#2811), corrected
<...>description (#2812), and pipeline-unwrap hint (#2806) were already reflected.