Skip to content

fix(testing): require 5 interleaved benchmark runs per side #38

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
mosobande merged 1 commit into from
Oct 20, 2026
Merged

fix(testing): require 5 interleaved benchmark runs per side #38

Show file tree
Hide file tree
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
5 changes: 5 additions & 0 deletions .changeset/benchmark-run-count.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"tech-stack": patch
---

Benchmark comparisons need at least 5 interleaved runs per side, up from 3.
2 changes: 1 addition & 1 deletion skills/tech-stack/references/practices/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,4 +35,4 @@
- Record an engine-exit diagnostic that cannot be fixed in an exact-match allowlist: message, resource path, count. Every other ERROR/WARNING fails.

## Performance comparisons
- Interleave baseline and candidate runs on the same machine, at least 3 runs each (Alárinà requires 5). Report median and p95 with ranges; serial batches can turn time-dependent noise into a false regression.
- Interleave baseline and candidate runs on the same machine, at least 5 runs per side. Report median and p95 with ranges; serial batches can turn time-dependent noise into a false regression.