Skip to content

[feature not live] docs(merge-queue): add Testing Duration chart to metrics page #647

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

Closed
samgutentag wants to merge 3 commits into from
+59 −9
Closed

[feature not live] docs(merge-queue): add Testing Duration chart to metrics page #647

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a9cacf5
docs(merge-queue): add Testing Duration chart section to metrics page
claude May 9, 2026
ca90308
docs(merge-queue): merge in narrative bits from #649
samgutentag May 12, 2026
d1080f4
docs(merge-queue): address PR review feedback
samgutentag May 12, 2026
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
42 changes: 42 additions & 0 deletions merge-queue/administration/metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,48 @@ The time in queue can be displayed as different statistical measures. You can sh
| P95 | The value below 95% of the time in queue falls. |
| P99 | The value below 99% of the time in queue falls. |

### Testing duration

Testing duration shows how long each PR spends in the TESTING state within the Merge Queue, measured from when testing begins to when the cycle reaches its final state. Unlike the Conclusion count and Time in queue charts, testing duration uses separate data bucketing — hovering over a data point will not highlight the corresponding point on the other charts.
Comment thread
samgutentag marked this conversation as resolved.
Outdated

Each data point represents one TESTING-to-final-state transition. A single PR can contribute multiple data points if its testing cycle restarted.

The stat measures match those on the Time in queue chart:

| Measure | Explanation |
| ------- | ----------- |
| Average | Average testing duration during the time bucket |
| Minimum | The shortest testing duration in the time bucket |
| Maximum | The longest testing duration in the time bucket |
| Sum | The total of all testing durations added together |
| P50 | The value below which 50% of testing durations fall |
| P95 | The value below which 95% of testing durations fall |
| P99 | The value below which 99% of testing durations fall |
Comment thread
samgutentag marked this conversation as resolved.
Outdated

#### Filters

Two dropdowns let you narrow the data shown in the chart:

**Outcome** — filter by how each testing cycle ended:

| Value | Meaning |
| ----- | ------- |
| All Outcomes | Include all testing cycles (default) |
| Passed | Cycles where tests passed |
| Failed | Cycles where tests failed |
| Interrupted | Cycles interrupted before completion |
| Cancelled | Cycles cancelled before tests ran to completion |
Comment thread
samgutentag marked this conversation as resolved.
Outdated
Comment thread
samgutentag marked this conversation as resolved.
Outdated

**Cycle ended in** — filter by how the PR's overall merge cycle resolved:

| Value | Meaning |
| ----- | ------- |
| All | Include all PR cycles (default) |
| Merged | PR was ultimately merged |
| Failed | PR ultimately failed out of the queue |
| Cancelled | PR was cancelled |
| In Flight | PR cycle is still in progress |

### Drill down into metrics

From the **Conclusion count** and **Time in queue** charts, you can drill into any point or window on the graph to see the exact pull requests that made up those numbers.
Expand Down
Loading