bazel-contrib / bazel-contrib/rules_python
Python coverage
- Dominant language
- Starlark
- Stars
- 688
- Forks
- 721
- Avg merge
- 15h 7m
- Merged PRs (30d)
- 76
Description
Upgrading rules_python in Bazel and running tests again version 0.36.0 showed problems with coverage support.
To reproduce run `bazel test //src/test/shell/bazel:bazel_coverage_hermetic_py_test` from Bazel repository. It fails saying the test has failed, but this previously with builtin Python rules wasn't the case.
I went down the rabbit hole, but I couldn't figure it out. I think that this test should be moved out of Bazel into rules_python, if it isn't already.
Contributor guide
Research direction
Reproduce the failure with `bazel test //src/test/shell/bazel:bazel_coverage_hermetic_py_test` from the Bazel repository. Read the existing coverage test and rules_python coverage support to determine whether the test belongs here or in rules_python. Done means the test has a clear home and the coverage behavior no longer reports the unexpected failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100