Skip to content

fix: use distinct critcmp group names for PR benchmark comparison#72

Merged
deepjoy merged 1 commit into
mainfrom
fix-benchmark-comparison
Mar 22, 2026
Merged

fix: use distinct critcmp group names for PR benchmark comparison#72
deepjoy merged 1 commit into
mainfrom
fix-benchmark-comparison

Conversation

@deepjoy
Copy link
Copy Markdown
Owner

@deepjoy deepjoy commented Mar 22, 2026

Summary

  • The cached main baseline and the PR benchmark results were both saved under the critcmp group name current, causing critcmp to merge them into a single column instead of producing a two-column comparison with ratios.
  • Import the cached baseline under the group name main before comparing, so critcmp sees two distinct groups (main vs current) and renders a proper side-by-side diff.

The baseline and PR benchmarks were both exported under the group name
"current", causing critcmp to merge them into a single column instead
of producing a side-by-side comparison with ratios.
@deepjoy deepjoy enabled auto-merge (squash) March 22, 2026 02:38
@deepjoy deepjoy merged commit 61ce1ca into main Mar 22, 2026
1 of 2 checks passed
@github-actions github-actions Bot mentioned this pull request Mar 22, 2026
deepjoy added a commit that referenced this pull request Mar 22, 2026
- PR #72 introduced `critcmp --import` which doesn't exist, causing the
"Compare benchmarks" step to fail on every PR
- Pass the exported JSON files directly as positional arguments
(`critcmp baseline.json pr.json`), which is the supported way to compare
two baselines
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant