chore(key-wallet): loosen wallet recovery perf threshold to 70ms#663
Conversation
The existing <50ms bound is tight for shared GitHub-hosted Ubuntu runners, which regularly clock averages in the 50-60ms range and max samples up to ~70ms. The result is flaky CI with no regression to investigate — the test is gating on runner speed, not code. Bump the avg threshold to 70ms, matching observed worst-case behavior with a small cushion. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated the wallet recovery performance test acceptance criteria from < 50ms to < 70ms, including corresponding assertion messages and added inline comments documenting the threshold rationale for slower CI runners. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v0.42-dev #663 +/- ##
==========================================
Coverage 68.12% 68.12%
==========================================
Files 319 319
Lines 67660 67660
==========================================
Hits 46093 46093
Misses 21567 21567
|
Summary
Not a code-perf change, just a CI-stability fix. If real regressions land, the test will still catch them (a regression that pushed averages above 70ms on the same hardware would be significant).
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit