-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Memory regressions in daily benchmark #18569
Comments
Anyone has an idea about this? |
Did we trigger nanosoldier on all the intermediate commits to see which one it was? |
Commit range is ec3d29e...3a31155 |
@jrevels is there anyway to run nanosoldier on two arbitrary commits? |
Looks like you should be able to do that by commenting on a specific commit, and giving the reference commit via |
Yeah, just thought if I could do it here for example. |
f30c949#commitcomment-19082011 seems to suggest that up to that commit things are ok? |
Has this been figured out yet? |
I couoldnt reproduce this |
Putting it here so it doesn't get forgotten.
3a31155#commitcomment-19063411
https://github.com/JuliaCI/BaseBenchmarkReports/blob/c446686d038e02992f7b0a60490e04577069720f/daily_2016_9_17/report.md
Noticed by @Sacha0
The text was updated successfully, but these errors were encountered: