-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
Potential regression induced by PR #56037 #57366
Comments
My local asv benchmarking shows the regression was introduced in d9f70b3 rather than the previous commits
|
Thanks @rtlee9 - isn't that commit associated with the highlighted PR in the OP? |
Yeah I was just confirming it was that commit in particular, since the asv benchmarks had skipped a few commits
|
Ah - thanks for confirming. |
PR #56037 may have induced a performance regression. If it was a necessary behavior change, this may have been expected and everything is okay.
Please check the links below. If any ASVs are parameterized, the combinations of parameters that a regression has been detected for appear as subbullets.
Subsequent benchmarks may have skipped some commits. The link below lists the commits that are between the two benchmark runs where the regression was identified.
05c32ba...d9f70b3
cc @jbrockmendel
The text was updated successfully, but these errors were encountered: