Skip to content

Update documentation on Run durations in parallel runs #392

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nohwnd merged 1 commit into from
Jul 2, 2026
+1 −9
Merged

Update documentation on Run durations in parallel runs #392

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 1 addition & 9 deletions docs/usage/result-object.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -219,15 +219,7 @@ The good news is that **the result object has the exact same shape** as a sequen
This is the most important difference. Because files overlap in time, summing their durations would overstate how long the run actually took. So in a parallel run:

- **`Run.Duration` is the wall-clock elapsed time** of the whole run (`Now - ExecutedAt`), not the sum of the container durations.
- **`Run.UserDuration`, `Run.FrameworkDuration` and `Run.DiscoveryDuration` are still the cumulative work** summed across all workers.

As a result, the per-phase totals can **exceed** `Run.Duration` - that is expected, because several files were doing work at the same time. The `Duration = Discovery + User + Framework` identity that holds for a sequential run **does not hold** for a parallel `Run`. Per-container and per-test durations are unaffected: each reflects that worker's own time.

```powershell
# Parallel: UserDuration can be larger than the wall-clock Duration
$result.Duration # e.g. 00:00:04 (wall clock)
$result.UserDuration # e.g. 00:00:11 (work across all workers)
```
- **`Run.UserDuration`, `Run.FrameworkDuration` and `Run.DiscoveryDuration` are set to zero. Phase durations are still available per container, block and test.

### Container order is preserved, not finish order

Expand Down