-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove criterion-cycles-per-byte dependency and related benchmark measurement #995
Conversation
09f78c2
to
f0347f0
Compare
Codecov ReportPatch and project coverage have no change.
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## main #995 +/- ##
=======================================
Coverage 90.93% 90.93%
=======================================
Files 254 254
Lines 25972 25972
=======================================
Hits 23617 23617
Misses 2355 2355 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind adding a CI step in this PR to make sure the benchmark at least compiles?
f0347f0
to
e323f89
Compare
Thanks @zsol, I've added a CI step to build the benchmark suite without running it. |
e323f89
to
1bf7e15
Compare
I'm afraid I don't have access to a @zsol if this last build doesn't work, could we merge this without |
1bf7e15
to
b5e85e5
Compare
Yeah, I'm fine with removing cycles/byte actually; it was never accurate enough to be reliable in CI. |
b5e85e5
to
4cb9629
Compare
Done! Thanks |
Thank you! |
Summary
criterion-cycles-per-byte is not supported on non-x86_64 platforms, so
cargo test
cannot be run:This PR makes it conditional and allows the tests to run.