How can you have a file with the same name in the same package?

Which parser are you using? Do you have an example?

It is a .net project, with structure similar to:

/Project/FeatureOne/Validator.cs
/Project/FeatureTwo/Validator.cs

The namespace in each file with same name is different.

The coverage data is generated using coverlet collector.

That means you are using opencover parser?

Somehow your report does not declare the correct structure or the parser does not read it. Do you have an example report? You can strip it down to the two classes that are merged.

Sorry, misunderstood the question. I am using the COBERTURA parser.

This the part of the Cobertura report:

<class name="Project.FeatureOne.Handler" filename="D:\Solution\Project\FeatureOne\Handler.cs" line-rate="1" branch-rate="1" complexity="2">
  <methods>
    ...
  </methods>
  <lines>
    ...
  </lines>
</class&gt;
<class name="Project.FeatureTwo.Handler" filename="D:\Solution\Project\FeatureTwo\Handler.cs" line-rate="1" branch-rate="1" complexity="2">
  <methods>
    ...
  </methods>
  <lines>
    ...
  </lines>
</class&gt;

drulli, Is there any chance this gets ever looked into? No pressure, just need to make some decisions on our end as this issue makes the plugin a lot less useful for us (invalid numbers reported, false positives on quality gate thresholds).

Thanks for pinging, it seems that I forgot about this issue. After reading it again, I think it is a duplicate of one of the problems reported in JENKINS-73175 which I fixed in https://github.com/jenkinsci/coverage-model/pull/113/commits/c6e6915c5763a510ef6cf7bb91c769e994fd5ca6. Can you please check if the problem is fixed in https://github.com/jenkinsci/coverage-model/releases/tag/v0.44.0 and https://github.com/jenkinsci/coverage-plugin/releases/tag/v1.15.0?

Thanks! I will verify it but it will take some time before I get our build server upgraded. Will get back to you. Thanks for all the hard work!

Just to follow up, I was not able to confirm as CloudBees is not yet supporting the latest version of the plugin: https://docs.cloudbees.com/plugins/ci/coverage

Version 1.16.1 is now available in CloudBees. I was able to verify that the issue is now resolved. Once again thank you drulli!