Currently, SonarCloud does not show coverage analysis on each pull-request

SonarQube Cloud
, , ,
1

Hi team, I have problems displaying source code coverage in each PR on SonarCloud.

  • The last time I updated the PR to display coverage information on SonarCloud, everything was fine as shown in the image below

    image
    image1136×621 29.9 KB

  • But today, PR coverage is not displayed even though I didn’t change anything. Will anything change on SonarCloud that affects this?

    image
    image896×678 33.3 KB

My config in sonar-project.properties

sonar.projectKey=LONGDSS_project-authz-authn
sonar.organization=longdss
sonar.projectName=project-authz-authn
sonar.javascript.lcov.reportPaths=coverage/lcov.info
2

What do the logs say about the import of code coverage?

Do they look different between the two runs?

3

Thanks for your reply. I compared the successful log runs and failed log runs on Github Actions, they don’t differ in any way, so it caused me some confusion

4

I am facing the exact same issue for all of my python repositories. The code coverage info is missing from the Pull Requests. It was working before and no change was made to the configuration.

I also checked the scanner logs from before/after this issue started happening and there is no error or difference I could find.

Any advice would be greatly appreciated!

5

I can reproduce this on a “0 new lines” PR internally, so I’m flagging this for the relevant team.

If you experience this on any PRs with more than 0 new lines, let me know.

8

@shijigopinathan Sorry for the late reply, I’m having the same problem as you, but I used a small trick which is to add a new line of code to analyze coverage
=> SonarCloud will analyze that new part of your code. At the same time, display both coverage for new code and coverage for the entire code
Although it is only a temporary solution, I hope my answer is useful to you

9

@Colin Thank you. Currently I only encounter this situation with PRs that only have 0 new lines code, PRs that have new code will work normally.

10

Yes, it’s the same for me too. Thank you! Hopefully this issue will be fixed soon.

12

Hello,

This is indeed a bug, we have created a ticket internally to resolve this.

Thanks,

16

any update on the ticket you opened ? I am still facing the same issue.

17

@richardo_sm They said it was a bug and created a ticket, but it doesn’t seem to have been fixed yet

18

It’s still scheduled for the end of this month. Thanks for your patience.

19

It’s July now, has this been fixed?

20

@glau2 Until now, I still get this error

21

It has not been fixed yet. It is still scheduled for the next hardening sprint.

22

Hello,

Is this still being fixed? We appear to have experienced this as of a couple of days ago.

Thank you!

23

It still needs to be fixed, yes. Thanks for your patience.

24

Good catch. I was configuring Jacoco coverage for a Java project for first time and spent half a day figuring this out.
This issue is marked under JS/TS section but this is an issue for Java and I am assuming for every other language as well.
We would also appreciate if a possible timeline/fix date could be provided.
Thanks.

25

Hi, is there any update about the fix?

26

It’s still an open issue. I’m sorry I don’t have any more news to share.