On multiple lcov files for the same source files

SonarQube Cloud
,
23

Hey @eric.morand,

We ended up finding a workaround to this problem. In our case, we have two services with the same name. These services are in two completely different modules / folders, but it seems that Sonar would choke due to a possible name conflict. As a quick test, we changed the name of the two services and the coverage started to pick up again.

As for the public repo, I don’t have a ton of time to that right now, apologies.

1 Like
24

Thanks for the follow-up. It’s very interesting that Sonar coverage may confuse two modules sharing the same name. I’ll try to reproduce it.

For now, I’ll consider this ticket as solved. Whenever I have something to share about this “same name” issue, I’ll let you know here.

Again, thanks a lot for your time. :pray: