You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proving-ground complexity test currently asserts a strict wall-clock growth ratio while the full Vitest suite runs files in parallel. During PR #324 Code Lawyer checks, npm test failed repeatedly with ratios around 16.1-16.25 against the < 15 threshold, while npx vitest run test/proving-ground.test.js -t 'complexity' passed in isolation. The gate should verify sub-quadratic behavior without depending on incidental CPU contention from unrelated test files.
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Jun 1, 2026
🔗 Related PRs
#321 - [codex] Add isolated git-warp v17 upgrade harness [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
test: harden proving ground complexity gate (#325)