-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: add minimal requirements file #50339
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
Conversation
Love the idea - needed something similar for #50046 Wondering if we shouldn't make this actually a minimal requirements file though, which would exclude pytest-cov and pytest-xdist (I think only CI needs those). Might be nice to have a true minimal file and compose the CI required-elements on top of that |
aa69a7b
to
ba9e0dd
Compare
ba9e0dd
to
2fe4e02
Compare
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.
lgtm
Any other thoughts on this? @mroeschke @lithomas1 @fangchenli |
.github/workflows/python-dev.yml
Outdated
@@ -75,8 +75,7 @@ jobs: | |||
python -m pip install --upgrade pip setuptools wheel | |||
python -m pip install -i https://pypi.anaconda.org/scipy-wheels-nightly/simple numpy | |||
python -m pip install git+https://github.com/nedbat/coveragepy.git | |||
python -m pip install versioneer[toml] | |||
python -m pip install python-dateutil pytz cython hypothesis==6.52.1 pytest>=6.2.5 pytest-xdist pytest-cov pytest-asyncio>=0.17 | |||
python -m pip install -r ci/deps/requirements-minimal.txt pytest-cov pytest-xdist |
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.
On second thought, are you sure pytest-xdist is not required? I remember having to install it once for some test(it was using one of the pytest-xdist fixtures).
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 the S3 tests use the worker_id
pytest-xdist fixture. All of them should be marked with single_cpu
so I guess in this job those should be skipped. Might make sense to include pytest-xdist just in case anything changes
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
We've got 2 approvals on this. Rather then let it go stale let's merge in on next conflict fixup, unless someone objects |
This reverts commit b6f277c.
this workflow isn't actually running at the moment, so marking as draft until it's re-enabled #50696 (comment) |
closing to clear the queue, might pick it up again in the future |
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.