[emyller]

CodSpeed never benchmarks main: its run stays queued, as macro runner usage is exceeded, so PRs get no comparison.

Follows #272.

Changes

• Benchmarks run on ubuntu-latest instead of codspeed-macro.
• Benchmarks are measured in simulation mode instead of walltime.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 49 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: d101b272-c187-4746-9aec-b1256e89db7f

Commits

Reviewing files that changed from the base of the PR and between 2a69db4 and e8abaf1.

Files selected for processing: 1

• .github/workflows/codspeed.yml

Walkthrough

The benchmarks job now runs on ubuntu-latest. The CodSpeed action uses simulation mode. The benchmark command remains make benchmark.

Priority: Normal

Estimated code review effort: 1 (Trivial) | ~4 minutes

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Git: CodeRabbit could not clone the repository, so clone-backed analysis was skipped and this review may be incomplete. Verify repository clone access, such as SSH credentials, before requesting another full review. If clone access is intentionally unavailable, use path_filters to narrow the review scope.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Additional comments: 1

.github/workflows/codspeed.yml-37-37: 1

37-37: Minor · Potential issue · Quick win

Unverified finding
We couldn't verify this from the code. It is shown for review, not as a verified issue.

The action now requests simulation mode while retaining make benchmark; if that target runs benchmarks instrumented only for walltime collection, the action may collect no usable simulation results.

The run fails or publishes no benchmark measurements, leaving PRs without comparisons despite the runner change.

This can occur when: A benchmark workflow run executes a make benchmark target whose benchmark framework or CodSpeed integration does not support simulation mode.

---

Review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 95292818-36a5-4745-b857-f4805a2d6f4d

Commits

Reviewing files that changed from the base of the PR and between 701e8e5 and 2a69db4.

Files selected for processing: 1

• .github/workflows/codspeed.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

[codspeed]

Congrats! CodSpeed is installed 🎉

🆕 15 new benchmarks were detected.

You will start to see performance impacts in the reports once the benchmarks are run from your default branch.

Detected benchmarks

• test_get_environment_flags[large]: 497.8 µs
• test_get_environment_flags[medium]: 249.4 µs
• test_get_environment_flags[small]: 213.8 µs
• test_get_identity_flags_no_traits[large]: 374.1 µs
• test_get_identity_flags_no_traits[medium]: 288.6 µs
• test_get_identity_flags_no_traits[small]: 883.5 µs
• test_get_identity_flags_with_identity_overrides[large]: 530.2 µs
• test_get_identity_flags_with_identity_overrides[medium]: 524.9 µs
• test_get_identity_flags_with_identity_overrides[small]: 998 µs
• test_get_identity_flags_with_traits[large]: 727.1 µs
• test_get_identity_flags_with_traits[medium]: 307.7 µs
• test_get_identity_flags_with_traits[small]: 1.2 ms
• test_get_identity_segments_with_traits[large]: 37.9 ms
• test_get_identity_segments_with_traits[medium]: 6.2 ms
• test_get_identity_segments_with_traits[small]: 2.1 ms

---

[khvn26]

Let me know if my suggestions make sense to you.