test: tighten post-fix macOS performance budgets (Fixes #507) - #508
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Performance Report (Linux)Result: ✅ Within regression budgets
|
Test Coverage Report (Linux)Result: ✅ Within regression budget
|
Performance Report (macOS)Result: ✅ Within regression budgets
|
Performance Report (Windows)Result: ✅ Within regression budgets
|
Test Coverage Report (Windows)Result: ✅ Within regression budget
|
There was a problem hiding this comment.
Pull request overview
This PR recalibrates macOS performance regression budgets used by PET’s quality snapshot comparator now that the deterministic 30s cold-refresh tail was removed in #506, ensuring future multi-second drift is caught while staying tolerant of hosted-runner variance.
Changes:
- Tighten macOS P95 regression budgets for server startup, full refresh, and time-to-first-env in the snapshot comparator.
- Add unit tests proving an observed post-fix run stays within the new budgets and that synthetic multi-second regressions now fail.
- Update quality snapshot documentation to reflect the new macOS budgets and recalibration rationale.
Show a summary per file
| File | Description |
|---|---|
| scripts/quality_snapshot.py | Tightens macOS P95 regression budgets in the comparator’s platform budget table. |
| scripts/tests/test_quality_snapshot.py | Adds tests validating new macOS budgets accept observed variance and reject multi-second regressions. |
| docs/QUALITY_SNAPSHOTS.md | Updates documented macOS budget values and adds recalibration notes. |
Review details
Tip
Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Suppressed comments (1)
docs/QUALITY_SNAPSHOTS.md:55
- “fixed by issue #504” is incorrect phrasing (issues don’t fix code). This should reference the PR/change that fixed the tail (e.g., #506), while optionally keeping issue #504 as the tracking issue.
The macOS cold-refresh tail fixed by issue #504 remains guarded by phase and locator distributions plus privacy-safe interpreter timeout counts.
- Files reviewed: 3/3 changed files
- Comments generated: 1
- Review effort level: Lite
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Review details
Suppressed comments (1)
docs/QUALITY_SNAPSHOTS.md:27
- The documentation still states that the budgets "reflect ... 11 consecutive main-branch baselines", but the macOS P95 budgets in the table are now calibrated from a different dataset (three unchanged-content PR runs + an exact merged baseline). Consider updating the wording to explicitly note this exception so readers don’t assume the macOS P95 numbers came from the 11-baseline set.
Each cell is `absolute / relative`. The 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.
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.
- Files reviewed: 3/3 changed files
- Comments generated: 0 new
- Review effort level: Lite
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Review details
Suppressed comments (1)
docs/QUALITY_SNAPSHOTS.md:26
- This paragraph cites issue #504 as the tracker for the macOS P95 budget recalibration, but this PR/issue context indicates the tightening work is tracked by #507 (while #504 tracks the original macOS tail). Updating the reference avoids confusing readers about which issue governs the budgets.
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.
- Files reviewed: 3/3 changed files
- Comments generated: 0 new
- Review effort level: Lite
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Summary
Recalibrate macOS P95 regression budgets now that #506 removed the deterministic 30-second interpreter-probe tail. The new limits preserve 4-6x observed hosted-runner variance while blocking multi-second drift that the old baseline-era limits allowed.
Changes
Validation
python -m unittest discover -s scripts/tests -p 'test_*.py' -v(22 passed)f0c62d9Fixes #507