Fix parallel run total durations#2807
Merged
Merged
Conversation
…ners Summing container durations overstates a parallel run because the files overlap in wall-clock time. Use the orchestrator's measured elapsed time for Run.Duration in parallel, and blank the per-phase run totals (user, framework, discovery) - a single wall-clock figure for those isn't meaningful once the files overlap. The per-phase breakdown still lives on each container, since parallelism is file-level. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summing container durations overstates a parallel run — the files overlap in wall-clock time, so two 1s files don't take 2s. Use the orchestrator's measured wall-clock for
Run.Durationin parallel instead.The per-phase run totals (
UserDuration,FrameworkDuration,DiscoveryDuration) are blanked in parallel rather than summed. A single wall-clock figure for those isn't meaningful once the files overlap, and the breakdown still lives on each container since parallelism is file-level.Sequential runs are unchanged —
Run.Durationthere is still the sum of the containers, which a result-object test pins down.Supersedes #2802.
Fix #2794