Bump typeberry long-running fuzz to 100k blocks per spec#92
Conversation
Both tiny and full now run a single 100k-block pass against graymatter source. Timeout bumped from 30m to 23h to fit the larger run, matching the turbojam-fuzz precedent. 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)
📝 WalkthroughWalkthroughThe typeberry-fuzz GitHub Actions workflow is updated to standardize block load at 100,000 for both matrix specs and adjust execution timing: timeout is extended to 1,380 minutes (23 hours) and the run count is reduced to 1. ChangesTypeberry Fuzz Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
num_blocks: 100000for bothtinyandfullspecs.num_runsfrom 9 to 1 (single straight pass per spec instead of repeated source restarts).timeout_minutesfrom 30 to 1380 (23h), matching the precedent inturbojam-fuzz.yml.Test plan
workflow_dispatchrun ontinycompletes within the new timeout.workflow_dispatchrun onfullcompletes within the new timeout (this one is the risk —fullwas previously ~10× slower per block).🤖 Generated with Claude Code
Summary by CodeRabbit