-
-
Notifications
You must be signed in to change notification settings - Fork 519
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
JSON output is missing data when using --parallel #1295
Comments
This is a known gap, please feel free to file a PR to solve it, thanks! |
Could someone take a look at #1309 and tell me whether I'm on the right track? If so, I will finish the PR. |
Commented 👍 |
When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output.
When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output.
When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output.
When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output.
When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output.
When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output.
When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output.
When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output.
* Correct ``--result-json`` output with ``--parallel``. (#1295) When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output. * avoid duplication in code, improve coverage
Sorry to hijack this thread, but is there a way to put |
@con-f-use sadly at the moment there isn't 🤔 |
When using
--parallel
with--result-json
, then the resulting output only contains a setup step and nothing else.tox.ini
setup.py
test_parallel.py
tox --parallel auto --result-json parallel.json
% tox --result-json serial.json
With tox 3.7.0 the output contained even less:
The text was updated successfully, but these errors were encountered: