-
Notifications
You must be signed in to change notification settings - Fork 50
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
[Meta] Test optimizations #830
Comments
I'm curious what version of pytest-celery you were using. the environment-dev.yaml file gets the version on conda-store which is not up to date (0.0.0a). The current version on PyPI is >1.0.0. Tests seems to run slower on the 1.0.0 version though. |
I am just using the |
Okay, we are already in a much better state at this point after dealing with the worst offenders: Test times
|
Recently, we saw failures in two unit tests that are calling out to
|
Most of the speedup this issue was intending to target has been achieved. Let's revisit this in the future, as the test suite is poised to undergo significant changes in the coming months. |
Context
I'm running tests locally, following the steps in
test_conda_store_server_unit.yaml
workflow. The unit tests for conda-store-server take a long time. Insideconda-store-server/
, I ranpytest --durations=0 -m "not extended_prefix and not user_journey" tests
and recorded the following durations:Click to expand output
A number of tests failed due to a 400 error:
Still others error out because of a storage issue:
But in either case I think we have a better idea of the tests that are really slowing down CI.
Here's the test summary:
Value and/or benefit
Faster tests mean less energy spent per run, lower waiting times, and quicker turnaround.
Anything else?
test_generate_constructor_installer
Accounted for 64% of the total test time.The text was updated successfully, but these errors were encountered: