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
Cannot collect tests : pytest.PytestDeprecationWarning #10275
Comments
Hey,
-python
Also, I don't know if this is a related issue or not, but when I try to run the tests from setup.py with: I get the error: I'm using: |
@taldcroft , please downgrade to pytest 5.3 |
@Iamsoto , |
@taldcroft - I'm having the same issue - the other option is to temporarily remove If we do not have them already, I guess we should be having some cron CI runs on our pytest extensions with |
Shouldn't the documented pip install command install an acceptable version of pytest? |
Let's close this as duplicate of #10039. The issue is with the plugin, which has been fixed, but other issues arose with its new release, thus the release has been reverted to avoid confusion about CI failures during the postponed feature freeze frenzy. Now the discussion is ongoing about the right way to proceed in a few other recent issues and PRs. As a workaround please downgrade and use pytest 5.3 for now. |
The docs certainly can point out the very pinfile tox uses for CI. Duplicating the pinnings in the docs I don't think is practical though. |
We indeed do keep an eye on new versions, both pytest and sphinx releases are reported on slack, and this issue is widely known an talked about a bit, and in fact fixed, but given this week wasn't the calmest; rolling out the fix has been reverted as other issues have came to light due to the fix. |
@bsipocz - absolutely, and no worries! |
This is all a bit beyond me, but is it possible to have pinned test dependencies that get installed via |
I suppose in this situation the best would indeed be to use tox to handle all the installations and environments. I don't think these temporary limitations are within scope of |
To be honest I don't understand what you said at all (in particular the second sentence). I'll say that What I also don't understand is that this issue is labeled a duplicate of #10039, but that issue is also closed but there is a real active problem at this moment, namely a user comes along and precisely follows the testing documentation instructions and then tests cannot be run. So I don't follow all the details but don't understand how the user is supposed to know to downgrade pytest. |
Maybe a more useful question is - how can I make an interactive working environment that is the same as what I am in a state right now where This is what I am getting with the environment I created in the original description, but with pytest downgraded to 5.3. I don't get that error before #10210, but that might be a red-herring to some other problem. |
That issue is closed as this is upstream, a compatibility issue between pytest-doctestplus 0.5 and pytest 5.4. We do close all other unrelated upstream issues and report them in the relevant upstream repos instead, too, I don't see why testing related ones should be different. To reuse the env: tox creates a the version limitations otherwise live in this file: https://raw.githubusercontent.com/astropy/ci-helpers/master/pip_pinnings.txt |
@taldcroft , it wasn't explicitly documented because it's a temporary problem that is hopefully fixed by now (?). The timing of freeze and breakage coinciding was really unfortunate. On hindsight, maybe there should have been a pinned issue about it. Also we turn all warnings into error in |
Absolutely need to have |
I also completely agree on turning warnings into errors, that was never in question. I have been just suggesting that the environment installed by And don't get me wrong, I stand in awe and admiration for the infrastructure team doing all these things I can't even imagine and fighting the constant battle to keep it all together. It's just a tough position where anything less than perfect can end up being a show-stopper. |
Was about to add to this, but really this is best done in a new issue - #10303. If someone explains how to do it there, I'll volunteer for adding it to the documentation. |
Description
I have no idea what's happened to my setup, but suddenly nothing is working. I tried now started entirely from scratch, including removing my ~/.astropy and making a fresh env for testing.
Test collection fails early with:
Steps to Reproduce
System Details
Darwin-19.2.0-x86_64-i386-64bit
Python 3.6.10 |Anaconda, Inc.| (default, Mar 25 2020, 18:53:43)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)]
Numpy 1.18.3
astropy 4.1.dev1534+g7d2a91538.d20200502
The text was updated successfully, but these errors were encountered: