Skip to content
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

Set number of cores to 1 when running tests #11

Closed
2 tasks
redeboer opened this issue Aug 6, 2020 · 0 comments · Fixed by #140
Closed
2 tasks

Set number of cores to 1 when running tests #11

redeboer opened this issue Aug 6, 2020 · 0 comments · Fixed by #140
Assignees
Labels
🖱️ DX Improvements to the Developer Experience
Milestone

Comments

@redeboer
Copy link
Member

redeboer commented Aug 6, 2020

As noted in ComPWA/expertsystem#108 and ComPWA/expertsystem#138, test coverage as computed by pytest-cov decreases if running on multiple cores. This causes a mismatch of test coverage computed on CI and computed locally (if run on multiple cores). It would be better if all tests run single core. Question is, how to do this in a DRY way?

Current proposal:

@redeboer redeboer transferred this issue from ComPWA/expertsystem Apr 6, 2021
@redeboer redeboer added the 🖱️ DX Improvements to the Developer Experience label Apr 16, 2021
@redeboer redeboer added this to the 0.9.6 milestone Jan 22, 2022
@redeboer redeboer self-assigned this Jan 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖱️ DX Improvements to the Developer Experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant