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
Version 2.0.0 may trigger internal error on Python 3 #580
Comments
Hi @McSinyx, Unfortunately that's a generic "something bad happened while sending tests to the worker", and has a large number of possible causes (some of them not even related to pytest-xdist). Can you provide a reproducible example? |
Thank you for the prompt response. As for reproducibility, I can't make the error appear on my machine, but the CIs consistently show the error since last night and pytest-xdist happens to have a new release recently. I thought that the ambiguous errors above would contain some obvious information to the pytest team but I guess my imagination is too wild 😄 To be fair pip is using a quite obsolete combination of version for pytest and its plugins and pinning pytest-xdist to 1.34.0 appears to solve the issue. I don't speak for the maintainers of pip but I think it is not urgent at all to have the root cause discovered/fixed in the next few months (until pip drops Python 2 support). Edit: Using latest pytest (instead of <5) also makes the CIs green. Please feel free to edit the title or close this issue, whichever you think is better. |
I'm seeing this consistently in SciPy Azure CI since the latest This is observed on Windows only I think. |
See PR here for example: scipy/scipy#12667 Note that those logs can disappear pretty quickly |
@nicoddemus Looks pretty reproducible for SciPy, but replicating our exact CI environment may take devs a fair bit of time on Windows. Forking SciPy repo and setting up Azure CI on the fork is what I do in these cases. |
This works around the incompatibility of pytest-xdist 2.0.0 with older pytest: pytest-dev/pytest-xdist#580
This works around the incompatibility of pytest-xdist 2.0.0 with older pytest: pytest-dev/pytest-xdist#580
This issue looks like its an issue in pytest 5.4.3, upgrading to 6.0.1 fixed the issue for my team. |
Confirming this is is happening to us for some older maintenance releases of ours that are pinned on pytest<6.0.0 Have reproduced on fedora 32 and centos8 and rhel8, so no special platform issue. These are all using python 3.6. For those maintenance releases we've pinned pytest-xdist to 1.34.0 and now are avoiding problem. Is there some way to warn that pytest-xdist>2.0.0 requires pytest>=6.0.0 ? Not a problem on unpinned pytest and pytest-xdist in our devel branch. |
setup.py should handle this: https://github.com/pytest-dev/pytest-xdist/blob/master/setup.py#L3 |
Hello there, we have just encountered this issue running CIs for pip on Python 3:
Regarding the error, I found this StackOverflow thread but I'm not sure if it is still applicable to current pytest-xdist.
The text was updated successfully, but these errors were encountered: