build: fix building benchmark#532
Merged
Merged
Conversation
d71721e to
8163129
Compare
Claude review of PR #532 (4ff0525)Suggestions
Nits
|
Contributor
|
Thanks! For bf-bencher, could you instead add a flag like --fail-on-last-commit-fail? We can have failing benchmarks from time to time in a PR for example, as long as the last commit can be built and benchmarked. |
8163129 to
1214f34
Compare
1214f34 to
1d237a3
Compare
1d237a3 to
4ff0525
Compare
qdeslandes
requested changes
May 12, 2026
4ff0525 to
5519b23
Compare
qdeslandes
approved these changes
May 12, 2026
Contributor
qdeslandes
left a comment
There was a problem hiding this comment.
Alright, lgtm! Thanks for fixing this!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
benchmark_bincurrently cannot be built:tools/benchmarks/main.cpphas been broken sincelib: rule: convert counters bool to a uint8_t bitfield(0e6c660, 2026-05-08), which updatedtests/harness/Rule.hppbut didn't update the benchmark file. Result: every benchmark CI run since then has been silently skipping the benchmark, loading latest results (from 2026-05-08), and reporting "no significant change", i.e. green, for them.Example: https://github.com/facebook/bpfilter/actions/runs/25743097177/job/75598766760
This PR fixes
main.cpp, and updatesbfbencherscript so that it should fail when it fails to benchmark something.