-
Notifications
You must be signed in to change notification settings - Fork 1.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
Enable performance tracking via continuous benchmarking. #13460
Conversation
CodSpeed Performance ReportCongrats! CodSpeed is installed 🎉
You will start to see performance impacts in the reports once the benchmarks are run from your default branch.
|
@@ -210,11 +214,11 @@ def test_env_remove(conda_cli: CondaCLIFixture, tmp_env: TmpEnvFixture): | |||
assert not code | |||
|
|||
|
|||
@pytest.mark.benchmark |
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.
In the future I'd rather see a tests/benchmarks/
directory with benchmark-focused tests so we don't mix IO too much, since codspeed since to be focusing on CPU bound tasks.
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.
Yeah, that makes sense, I even started with it at first and then noticed that I was duplicating a lot of efforts. I started from the tests in conda-benchmarks, but thought to first get some experience with codspeed.
Co-authored-by: Ken Odegard <kodegard@anaconda.com>
Description
This sets up codespeed following their docs: https://docs.codspeed.io/ci/github-actions
I've selected a number of basic tests to run for now, we can tweak that list in the future.
Checklist - did you ...
news
directory (using the template) for the next release's release notes?[ ] Add / update outdated documentation?