-
Notifications
You must be signed in to change notification settings - Fork 347
Running under xdist causes FileNotFoundError #720
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
Comments
I guess this is related to pyyaml being available on the host, but not the nodes? |
At this point I was just running it on my local (macOS) machine, using e.g. |
I tried bypassing that particular execution path altogether by setting |
Try upgrading Python. |
I will try it, although unfortunately we're pretty well stuck on 3.4.3 for the moment for infrastructure reasons. It'll at least be a good data point—that issue does look related. I'll report back, hopefully today or tomorrow. |
Renamed the issue to be more general and better correlate those things |
Upgrading to 3.5 appears to have mitigated this issue, so it looks like that's the issue. Thanks for pointing me in that direction! |
Hey! I've just gotten a big project onto pytest and now I'm working on speeding up the test suite. Running an otherwise working suite using pytest-xdist with any number of workers causes an error via pytest-django when Django tries to load PyYAML for serialization:
Django's docs state:
But this occurs whether PyYAML is installed or not. I'm filing here because it feels like a variation pytest-django is creating in the presence of xdist, but I'd be happy to file in pytest-xdist if it appears more likely to be implicated. Thanks for any help you can provide!
Python: 3.4.3
Django: 1.11.20
pytest: 4.4.1
pytest-django: 3.4.8
pytest-xdist: 1.28.0
PyYAML: 5.1.0
Databases: Postgres and MySQL
The text was updated successfully, but these errors were encountered: