All coverage on LedgerSMB/LedgerSMB reported as new

[ehuelsmann]

Hi,

Until a few days ago, coverage was nicely reported relative to the last coverage report and the background of the 'master' branch was showing an increasing graph. Now, the graph is gone and all coverage is reported as "new coverage".

Please advise!

Thanks in advance,

Erik.

[dasfrosty]

I'm getting similar weirdness. I keep getting multiple notification emails saying "First build on <branch-name>" for the same branch repeatedly.

And now I just got a notification for build #1 with no branch information at all! To be specific we were on build #326, but then coveralls just created a new build that is labelled build #1. The oldest saved build prior to that was #43.

(https://coveralls.io/builds/5350685 ← access restricted)

[wjwarren]

Same thing happens to my builds too.

Coverage remained the same on ​_[repo]​ ​[branch]_​ from ​_0.0%​ to ​[X]%_​

Similar reported issue: #738

[greatislander]

Confirmed for https://github.com/pressbooks/pressbooks too, e.g.: https://coveralls.io/builds/5399979

[greatislander]

Any news on this issue?

[ehuelsmann]

@greatislander sent a support request through the Coveralls Feedback functionality on March 6. Then sent a reminder 10 days later. Got a response from @nickmerwin telling me a fix had been deployed and needed to be confirmed. Within 2 days, I responded back that the issue is not fixed. Unfortunately, no reaction since then, despite reminders :-(

[daurnimator]

I'm getting same issue on https://coveralls.io/github/daurnimator/lua-http

[nickmerwin]

Hi all, we're deployed a fix for this. Could everyone check and confirm?

Close for now.

Thank you!

[daurnimator]

It's fixed on the main page for the project, but it's now weird on the per-build page. e.g. https://coveralls.io/builds/5813606 for this build:

• on the main page it showed "-" i.e. no significant change in coverage
• in the build matrix it's showing an increase in coverage for every item in the matrix
• in the per-file table it's showing a decrease in every file.

[nickmerwin]

Hi @daurnimator it looks like that was cached content, now it's showing all unchanged coverage levels.

[daurnimator]

ack.

[wjwarren]

Looks good for me too, thanks! 😄