-
-
Notifications
You must be signed in to change notification settings - Fork 438
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
Coverage suddenly missing everywhere but unit test modules #1580
Comments
I notice that your pip freeze output doesn't mention "coverage"? Are you sure you are using the same version? You mention 6.5.0, but perhaps it is different in the working and non-working scenarios? I'm not sure how to help without a reproducible case. |
Hi @nedbat, Sorry, when I copied from Github Actions, it seems like the selection from the Log Viewer missed most a chunk of the packages. I have updated the OP using the raw logs and I can confirm that they are the same in both scenarios: The packages differences are as follows:
|
Do you have any more information about how I might be able to reproduce this? Can you link us to the repo with the code? |
Hi @nedbat, The code is here:
We for now only upload coverage from macOs and Python 3.11 as Windows and Linux seemed to be affected. Cheers, Thomas |
Describe the bug
Hello,
We have had a dramatic reduction in coverage for about a month and I'm not sure what is the issue. We basically lost coverage everywhere but in the unit test modules. It is very similar to this issue: #1520. It started on Github Actions where we use the Linux build to report coverage.
There is no real difference between old "successful" builds and new "broken" ones. I managed to reproduce the behaviour locally on macOs and fixed it by using
sigterm = True
and I can confirm that it is now fixed on CI for macOs but Windows and Linux are still not showing the expected coverage.To Reproduce
How can we reproduce the problem? Please be specific. Don't link to a failing CI job. Answer the questions below:
coverage debug sys
is helpful. 6.5.0pip freeze
is helpful.Note that "successful" and "broken" jobs use for practical purposes the same packages.
I have unfortunately been unable to fix the issue anywhere but macOs by using
sigterm = True
pytest --doctest-modules --ignore=colour/examples --cov=colour colour
My
.coveragerc
file:Expected behavior
The coverage should have stayed the same and not changed.
Additional context
None at this point but happy to try as many things as required to understand what is going on.
The text was updated successfully, but these errors were encountered: