-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
parallel output does not respect --skip-missing-interpreters #1274
Comments
The same is true for platform mismatches. I have a
The relevant part of a
Errors are also handled as expected: I'd expect something like Running just plain |
This is a deal breaker for me on whether to use tox parallel mode. It would be great to utilize its performance, but reporting success on skipped environments is really not OK. I haven't digged in a tox code yet, but if someone can point me to where I should look, I might put together a pull request to resolve this. |
I just bumped into #1394, and it seems that this issue might be resolved during the rewrite leading to tox 4. It's probably good idea to wait for the tox 4 changes first. |
Did you try with |
Well yes, but that results in |
This would just be a partial workaround, but you could at least parallelize testenv creation, while still $ tox -p auto --notest --skip-missing-interpreters
$ tox --skip-missing-interpreters I did a quick test run with Django REST Framework on Python 3.7 - here are the results. Sequential: $ time tox --skip-missing-interpreters
...
real 3m42.750s
user 3m13.440s
sys 0m32.634s Parallelized venv creation/sequential test run: time sh -c 'tox -p auto --notest --skip-missing-interpreters && tox --skip-missing-interpreters'
...
real 2m37.989s
user 4m15.337s
sys 1m0.262s |
In case people have a desire to go for uglier workarounds, |
@rpkilby That's actually pretty good idea, at least for projects where testenv creation makes significant part of the test time. Thank you, I'll definitely try it out! |
This should have been fixed now with tox 4. |
Standard tox usage reports when a testenv was skipped due to a missing interpreter. This is included in both the live output, as well as the report summary at the end.
tox output
In comparison, tox in parallel mode simply shows success. It would be great if parallel mode also reported when a build was skipped due to a missing interpreter.
The text was updated successfully, but these errors were encountered: