bazel-contrib/rules_python

Empty coverage reports for Python 3.10.15 and 3.10.16

Open

#2844 aperta il 29 apr 2025

Vedi su GitHub
 (1 commento) (0 reazioni) (0 assegnatari)Starlark (705 fork)auto 404
help wantedtype: toolchain

Metriche repository

Star
 (679 star)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

🐞 bug report

Affected Rule

rules_python

Is this a regression?

No

Description

Running bazel coverage does not produce coverage reports for all versions of Python. The coverage.dat files are empty when using Python version 3.10.15 and 3.10.16. Other versions of Python 3.10 do seem to produce valid coverage reports.

I did not test Python 3.11 or 3.12.

🔬 Minimal Reproduction

I added tests on a fork of main: python-3-10-16-coverage.

Running

bazel coverage --action_env=COVERAGE_GCOV_OPTIONS=-b --combined_report=lcov --strategy=CoverageReport=local -- //test_code/...

from the tests/coverage directory returns a filled coverage.dat file in bazel-out for Python 3.10.14, but it is empty for 3.10.16.

🌍 Your Environment

Operating System:

Output of bazel version:

Rules_python version:

Anything else relevant?

Guida contributor