Skip to content

Commit 412b102

Browse files
karthiknadigCopilot
andcommitted
docs: identify macOS budget tracking issue (PR #508)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent e49ed76 commit 412b102

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎docs/QUALITY_SNAPSHOTS.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ A metric blocks when it exceeds both its absolute and relative budget:
2323

2424
Each cell is `absolute / relative`. The Linux and Windows budgets plus the macOS P50 budgets reflect observed GitHub-hosted runner variance from 11 consecutive main-branch baselines. Tighten them when a noisy path is fixed rather than normalizing a known regression into the baseline.
2525

26-
The macOS P95 budgets were recalibrated after PR #506 (tracking issue #504) using three unchanged-content pull-request runs and the exact merged baseline at `f0c62d9`. Their absolute headroom is four to six times the observed post-fix run-to-run range.
26+
The macOS P95 budget recalibration is tracked by issue #507 and follows PR #506's fix for issue #504. It uses three unchanged-content pull-request runs and the exact merged baseline at `f0c62d9`; the resulting absolute headroom is four to six times the observed post-fix run-to-run range.
2727

2828
The dual budget avoids failing on tiny percentage changes while still blocking material latency regressions. Tail metrics remain mandatory; a healthy median does not excuse a degraded P95.
2929

0 commit comments

Comments
 (0)