-
Notifications
You must be signed in to change notification settings - Fork 53
Enable tox --parallel #207
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
Conversation
I don't expect this to be useful without a GHA update, https://github.community/t/log-group-multiplexing/130543/5 |
Codecov Report
@@ Coverage Diff @@
## master #207 +/- ##
==========================================
- Coverage 83.30% 83.30% -0.01%
==========================================
Files 87 87
Lines 11579 11570 -9
Branches 1184 1184
==========================================
- Hits 9646 9638 -8
Misses 1815 1815
+ Partials 118 117 -1
Continue to review full report at Codecov.
|
GHA machines only have 1 cpu - so force parallelism
5434882
to
056000e
Compare
16c38ef
to
5d37253
Compare
run all python environments per OS VM
5d37253
to
ba778f5
Compare
55a7cc7
to
2a63a37
Compare
8d43123
to
1bc0aba
Compare
This reverts commit 2a63a37.
@adiroiban this might be nicer, what do you think? Currently we have to wait for the job to finish before seeing any output - https://github.community/t/log-group-multiplexing/130543/5 but maybe that's not so bad? |
if: startsWith(matrix.os, 'windows-') || startsWith(matrix.os, 'macOS-') | ||
run: echo '::set-env name=TOX_SKIP_ENV::pypy3.*' | ||
|
||
- name: build coverage for pypy3 # coverage doesn't like being built in parallel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- name: build coverage for pypy3 # coverage doesn't like being built in parallel | |
# coverage doesn't like being built in parallel, see https://git.io/JUdlT | |
- name: build coverage for pypy3 |
Takes about a minute longer overall, and the coverage change looks worrying |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think tox --parallel is ok for local builds.
For automated tests, I don't know if this help. I think that the VMs are 2 cores.... and a lot of tests are CPU intensive.
And is best if we see each environment as a separate status.
The coverage config change is ok.
I would say that is best to keep non-parallel runs for GHA runs.
Thanks!
Could do a run without |
@adiroiban tox without |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the test ;)
What I wanted to say, is that for GitHub Action we can have separate jobs for each environment.
But I am ok to run one job for each OS, and inside that job to test various Python version.
You can merge it as you think is best.
Thanks!
611cd2f
to
dc05885
Compare
@adiroiban hmm the coverage has gone down only on |
Thanks. I think that this can be merged. |
With credit to @graingert via twisted/ldaptor#207
Contributor Checklist:
docs/source/NEWS.rst
CONTRIBUTING.rst
.