-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix broken benchmark tests #1000
Conversation
1fd00e1
to
89cf8ef
Compare
385c5bf
to
7ebd55d
Compare
can we add ci-benchmark and push an empty commit (ie into development) to trigger generating new weights based on these changes as well? this would also confirm that running the benchmarks to generate weights works when it is run through the CI (I know you verified it runs manually but could be different) |
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.
other than rerunning weights, looks good to me
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.
LGMT, thanks!
rerunning. the failure was due to cancelling the benchmarking after almost 6h. how long does benchmarking usually take? 6h seems like a lot... cc @penumbra23 |
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.
Looks reasonable.
Not sure what the hold-up is here. Will merge it for now as this block my further work. @dvc94ch runtime-benchmarks will need to be addressed separately. |
Description
This PR fixes outdated/broken benchmark tests.
Fixes # (issue)
#997
Type of change
Code review prechecks: