-
-
Notifications
You must be signed in to change notification settings - Fork 436
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
assert line in analysis.missing
since coverage 7.6.2
#1896
Comments
Thanks, I can reproduce the problem. Now to understand why... |
@nedbat Thank you for looking into this. Just a heads-up, in case you need to use the repository in question again: I just merged a work-around (which is: using coverage 7.6.1) in the |
Note also that the assert fires on for i in(1, 2, 3, 4):
if True or False:
print("foo")
continue (see #198) |
Fixed in commit 2ace7a2. |
This is now released as part of coverage 7.6.8. |
Describe the bug
Running
python -m coverage lcov -o coverage.lcov
used to work just fine until coverage 7.6.1:This doesn't work since 7.6,2:
To Reproduce
How can we reproduce the problem? Please be specific. Don't link to a failing CI job. Answer the questions below:
Python 3.9, 3.10, 3.11, and 3.12.
coverage debug sys
is helpful.Since coverage 7.6.2 up to the latest 7.6.7.
pip freeze
is helpful.I am trying to send coverage report in LCOV format to coveralls.io from https://github.com/atlanticwave-sdx/pce (please excuse the prototype-iness), and running
python -m coverage lcov -o coverage.lcov
from CI jobs fails with a backtrace, as described above. This is reproducible in a local setup also. This library uses a dependency with a C extension (ortools), and I suspect that could be the problem, because other "pure" Python projects I work on are not affected.Using coverage 7.6.1 is the workaround.
git clone
,pip install
, and so on. Explain like we're five!Do this (assuming bash and Linux):
Expected behavior
Coverage should be able to produce an LCOV file without crashing.
Additional context
Unsure, sorry!
The text was updated successfully, but these errors were encountered: