Merge bitcoin/bitcoin#26158: bench: add "priority level" to the benchmark framework#1223
Merge bitcoin/bitcoin#26158: bench: add "priority level" to the benchmark framework#1223DashCoreAutoGuix wants to merge 1 commit intobackport-0.25-batch-480from
Conversation
WalkthroughThis pull request updates the benchmark macro API to accept an explicit priority level parameter, changes the BENCHMARK macro signature from Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~35 minutes
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: ASSERTIVE Plan: Pro 📒 Files selected for processing (44)
🧰 Additional context used📓 Path-based instructions (3)src/**/*.{cpp,h,cc,cxx,hpp}📄 CodeRabbit inference engine (CLAUDE.md)
Files:
src/bench/**/*.{cpp,h,cc,cxx,hpp}📄 CodeRabbit inference engine (CLAUDE.md)
Files:
**⚙️ CodeRabbit configuration file
Files:
🧠 Learnings (2)📓 Common learnings📚 Learning: 2025-07-28T23:09:09.522ZApplied to files:
🧬 Code graph analysis (1)src/bench/load_external.cpp (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
🔇 Additional comments (45)
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 |
Summary
Backport of bitcoin#26158
This adds a "priority level" to the benchmark framework, allowing
make checkto run only high-priority benchmarks whilebench_dashcan run all benchmarks.Changes:
BENCHMARK(n)macro toBENCHMARK(n, priority_level)for explicit priority setting> /dev/nullto suppress output duringmake checksanity checksTest plan
Notes
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.