Ned Batchelder

I'm not sure how to help without details of the segfault. Also, coverage.py 4.5.2 is almost five years old. Have you considered using a more recent version?

I've never used readme-coverage-badger, but at a glance, I don't see how it could change your coverage. Have you tried asking them about it? Also, you say you are using...

I usually start adding support for a version when the first alpha is released.

Thanks, yes. There are some odd problems reading frame objects in the C code, and I could use some help figuring it out.

Try setting the `[run] sigterm=True` setting (https://coverage.readthedocs.io/en/7.3.1/config.html#run-sigterm). If that doesn't help, share the code with us so we can look into it.

I haven't tried to reproduce this, but: the `[paths]` setting is only used by the `coverage combine` command. Can you try using that command to process the data files? Also...

Bug #1752 was recently fixed, but it doesn't improve this situation. Here the problem is this line: ``` Rule '*/demo' changed '/private/var/folders/_t/xpfjyxwx727_zrtwcrhyfyjm0000gn/T/tmp.DT7IE3yo/demo/__init__.py' to 'demo/__init__.py' which doesn't exist, continuing ``` The...

I'm going to close this: relative filenames are file names, not module names. I'm not sure how coverage could determine the relative file name to a file in a completely...

>> Perhaps some new setting like relative_to could complement relative_paths = true to enable this use case? > > Would this be worth considering? I don't use Bazel, so I...

Hi, can you provide us with code to run to demonstrate the problem? It's hard to debug your situation without it.