Add benchmark against latest release on main.#7753
Conversation
github-actions
bot
added
the
Automation
dcherian
force-pushed
the
benchmark-from-last-release
branch
from
a49085a to
e517c12
Compare
headtr1ck
left a comment
headtr1ck
left a comment
There was a problem hiding this comment.
That's a really good idea to prevent accidental regressions.
Is it possible to prevent the cancelling of this run when pushing another commit to main? This would be nice to trace the regressions.
Maybe this is not so important though since bulk PR merging usually happens with smaller PRs.
I assume that a decreased performance will result in a CI fail? Maybe we could automate this even more and automatically open an issue? But that can be done in another PR.
Thanks!
I think that's the default
Yeah but its a little flaky: https://labs.quansight.org/blog/github-actions-benchmarks so the noise might not be worth it |
* main: Bump codecov/codecov-action from 3.1.2 to 3.1.3 (pydata#7781) Fix whats-new [skip-ci] dev whats-new (pydata#7775) [skip-ci] Release 2023.04.2 (pydata#7774) Fix groupby_bins when labels are specified (pydata#7769) Docstrings examples for string methods (pydata#7669) Add dev whats-new Add benchmark against latest release on main. (pydata#7753)
2 participants
This adds a benchmark of
HEADvs the latest tag onmain.