Update to use coverage_output_generator-v2.8 #25200
Conversation
Built at commit ee12906 Relevant changes: * Add support for input FN lines that include a function end line (bazelbuild#25118) RELNOTES: LCOV parsing does not break on FN lines including an end line number
github-actions
bot
added
the
awaiting-review
|
@bazel-io fork 8.1.0 |
meteorcloudy
added
awaiting-PR-merge
github-actions
bot
removed
the
awaiting-PR-merge
Built at commit ee12906 Relevant changes: * Add support for input FN lines that include a function end line (bazelbuild#25118). RELNOTES: LCOV parsing does not break on FN lines including an end line number. Closes bazelbuild#25200. PiperOrigin-RevId: 723451534 Change-Id: I8912082ae6517bf0359329004d9a4f5e9ac76188
Built at commit ee12906 Relevant changes: * Add support for input FN lines that include a function end line (#25118). RELNOTES: LCOV parsing does not break on FN lines including an end line number. Closes #25200. PiperOrigin-RevId: 723451534 Change-Id: I8912082ae6517bf0359329004d9a4f5e9ac76188 Commit df92905 Co-authored-by: Charles Mita <[email protected]>
|
I know that the |
|
@c-mita What do you think of extracting coverage tools into their own module (possibly together with the test runners)? Then users could update independently from Bazel and architecture-specific builds such as native images would become usable. |
|
@aignas Hmm,, it's likely there will be no next minor release for Bazel 7, we should probably encourage people to migrate to Bazel 8? |
|
I agree about urging people to upgrade, but at the same time it usually takes a lot of time for people to upgrade. I think this particular change could be treated as a bug fix, so maybe it could fit into But if you have no plans to allocate resources for a patch release' I understand. |
Built at commit ee12906
Relevant changes:
RELNOTES:
LCOV parsing does not break on FN lines including an end line number.