PRs: "First build on master"

[hugovk]

I've noticed pull requests are no longer reporting coverage against the upstream master.

For example, this PR says:

coverage/coveralls — First build on master at 75.972%

This isn't much use. The check used to say how much the coverage had increased or decreased based on the upstream fork.

Is there some new setting or something missing from our repo/Coveralls configuration?

[julienbaley]

We're having exactly the same problem, no increase/decrease is reported as coveralls weirdly seem to believe this is the first build on master.

Can we get some help here? We're trying to keep coverage high by having a fail condition on coverage decrease, and those "first builds" break the feature.

[rwd]

Same here, on the 1246th build, making it difficult to enforce coverage.

[McPringle]

Still not fixed, the same happens here: This is our 109th build but the email says First build on develop …

[dougnukem]

I'm seeing a similar issue as well. Basically travis-ci "push" builds don't show difference in coverage, but "PR" builds do.

Is there any update is this a bad configuration that we can fix on our projects end?

Project: https://github.com/codingsince1985/geo-golang/
Language: Go
CI: Travis-CI
Coveralls Integration: goveralls and gover to aggregate coverage across multiple packages

• goveralls -service=travis-ci -coverprofile=gover.coverprofile

https://coveralls.io/github/codingsince1985/geo-golang?branch=master

• travis-ci "push" build saying "First build on master X%"
  • https://coveralls.io/builds/5801075 40th build
• travis-ci "PR" build shows code coverage diff
  • https://coveralls.io/builds/5788017

[nickmerwin]

Hey all, we've deployed a fix for this issue. Could everyone check and confirm?

I'll re-open if not.

Thank you!

[McPringle]

I can confirm that the fix worked fine for my last two pushes.

Thank you!

[homm]

Hi! We are experiencing the same issue again. python-pillow/Pillow#2060

[lthur]

We are experiencing the same issue right now.
It is everything ok?

[paltman]

We are experiencing this issue with one of our private repositories.

[hugovk]

Hey all, we've deployed a fix for this issue. Could everyone check and confirm?

I'll re-open if not.

@nickmerwin Please can you re-open this?

[Flamefire]

@nickmerwin Happening again

[jessica-pixvana]

Im having the same issue as @Flamefire