test: recalibrate Windows warm P50 budget (Fixes #513) - #515
test: recalibrate Windows warm P50 budget (Fixes #513)#515Karthik Nadig (karthiknadig) wants to merge 6 commits into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Test Coverage Report (Linux)Result: ✅ Within regression budget
|
Performance Report (Linux)Result: ✅ Within regression budgets
|
Performance Report (macOS)Result: ✅ Within regression budgets
|
Test Coverage Report (Windows)Result: ✅ Within regression budget
|
Performance Report (Windows)Result: ✅ Within regression budgets
|
There was a problem hiding this comment.
Pull request overview
This PR recalibrates the Windows warm Full refresh P50 regression gate used by the quality snapshot comparator, aligning it with observed schema-v2 runner variance while keeping other platform/percentile/cold/coverage/schema behaviors unchanged.
Changes:
- Updated the Windows warm Full refresh P50 dual regression budget from 50ms/30% to 150ms/50%.
- Expanded unit tests to prove a representative 182ms schema-v2 Windows run passes while a sustained 300ms median fails (without triggering unrelated gates).
- Documented the updated Windows warm P50 calibration provenance and the new budget in
docs/QUALITY_SNAPSHOTS.md.
Show a summary per file
| File | Description |
|---|---|
| scripts/quality_snapshot.py | Raises the Windows Full refresh P50 regression budget to reflect observed schema-v2 variance. |
| scripts/tests/test_quality_snapshot.py | Adds/adjusts tests to validate the new Windows warm P50 behavior (pass at 182ms, fail at 300ms, and “both budgets must be exceeded” coverage). |
| docs/QUALITY_SNAPSHOTS.md | Updates the published budget table and records the six-measurement Windows calibration set for issue #513. |
Review details
Tip
Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 3/3 changed files
- Comments generated: 0
- Review effort level: Lite
Summary
Recalibrate only the Windows schema-v2 warm full-refresh P50 budget after unchanged product runs exposed an unusually low exact baseline. The new limit accepts the measured 105-182ms range while still blocking a sustained median above 255ms against that baseline.
Changes
Validation
python -m unittest discover -s scripts/tests -p 'test_*.py' -v(35 passed)ad7ca1431524812300passed after retrying a transient baseline-download certificate failureSupersedes #514, which GitHub automatically closed when its stacked base branch was deleted.
Fixes #513