Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are a few of our pytest tests that are particularly slow (especially on the macOS and Windows runners).
We run several testenvs on each runner:
pyXX
: the default set of testspyXX-mistune0
: run with amistune<1.0
pin to test under mistune 0.xpyXX-notuils
: discovery of external utilities (e.g. ffmpeg, git) via PATH disabled to test that things degrade gracefully when to utitilies are not available (currently only run on the python 3.11 runners)pyXX-pytz
: run withpytz
installed (currently only run on the python 3.11 runners)pyXX-tzdata
: run withtzdata
explicitly installed (currently only run on the python 3.11 runners)The slow tests are slow because due to internet access, or spawning of new processes. We don't really get any benefit by repeating them on all of the above testenv variants.
This PR adds a
slowtest
pytest marker and applies it to those particularly slow tests which may be safely skipped in the variant testenvs.Tox.ini
is adjusted so that those tests are skipped for all but the mainpyXX
testenvs.This appears to speed the macOS job by a minute or more per testenv.
Issue(s) Resolved
CI tests are very slow