-
-
Notifications
You must be signed in to change notification settings - Fork 283
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
Fix coverage: use default file locations #565
Conversation
Welcome to Codecov 🎉Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment. Thanks for integrating Codecov - We've got you covered ☂️ |
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 the mkdir/find stuff was required so various coverage configurations via tox wouldn't overwrite one another 🤔
Ah right, happy to close this if someone would rather debug the combining. Alternatively, I'd probably factor the Django version into the matrix, so each is ran separately. This would also make good use of the 20 available parallel runners, also make it easier to see if something only failed for a single Django version. |
Yeah, probably a good idea, then just run |
Would you like to put together a PR? Feel free to push to this, re-use/copy commits, or start fresh :) |
@akx perhaps this CI file might help with some inspiration? https://github.com/django-parler/django-parler/blob/master/.github/workflows/tests.yaml This doesn't use tox, but let GitHub actions itself do the parallelization instead. |
Seems this would be worth merging as it is and then open a new issue for implementing the parallel CI/testing later. |
@Huge - Sounds good. I'll see if I can find some time this week to work on this. |
This fixes the coverage upload to Codecov.
Before
After
https://app.codecov.io/gh/jazzband/django-polymorphic/pull/565/tree