-
Notifications
You must be signed in to change notification settings - Fork 11
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
feat: Make cargo bench part of CI to ensure we don’t accidentally introduce performance regressions #257
Conversation
…sure-we-dont-accidentally-introduce-performance-regressions_2
…sure-we-dont-accidentally-introduce-performance-regressions_2
…sure-we-dont-accidentally-introduce-performance-regressions_2
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.
I have a few comments that I'll add to the PR later today.
…sure-we-dont-accidentally-introduce-performance-regressions_2
…sure-we-dont-accidentally-introduce-performance-regressions_2
Co-authored-by: Islam El-Ashi <[email protected]>
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.
LGTM!
chmod +x drun | ||
} | ||
|
||
get_correct_drun_release() { |
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.
nit:
get_correct_drun_release() { | |
maybe_download_drun() { |
Problem:
We are not checking if new PRs are introducing performance regressions.
Solution:
Add benchmark test to CI.