Skip to content

Cobertura line coverage results is wrong #274

Draft
akash-manna-sky wants to merge 10 commits intojenkinsci:mainfrom
akash-manna-sky:JENKINS-76232
Draft

Cobertura line coverage results is wrong #274
akash-manna-sky wants to merge 10 commits intojenkinsci:mainfrom
akash-manna-sky:JENKINS-76232

Conversation

@akash-manna-sky
Copy link
Copy Markdown
Contributor

Cobertura line coverage results is wrong

Fixes #253

Testing done

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests that demonstrate the feature works or the issue is fixed

@akash-manna-sky akash-manna-sky marked this pull request as ready for review March 1, 2026 06:36
@uhafner uhafner added the bug Bugs or performance problems label Mar 2, 2026
@uhafner
Copy link
Copy Markdown
Member

uhafner commented Mar 2, 2026

I'm not sure that the problem can be solved at all with the current implementation: the counters have the following semantics:

  • 0 / 0: No line coverage
  • 1 / 1: Line Coverage
  • 0 / n: No line coverage, no branches covered
  • m / n: Line coverage, m branches covered.

It is currently not possible to show line covered but branches are zero covered.

@github-actions github-actions bot requested a review from uhafner March 3, 2026 10:38
@uhafner uhafner marked this pull request as draft March 31, 2026 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Bugs or performance problems

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[JENKINS-76232] Cobertura line coverage results is wrong

3 participants