Always showing "First build on master at X%" on travis-ci push build

[dougnukem]

Not sure if this is a goveralls or coveralls issue, but I'm always seeing coveralls.io report a travis-ci "push" build as "First build on master X%" instead of showing the code coverage diff. I am seeing code coverage diff for pull-request "PR" builds from travis-ci.

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 at X%"
  • https://coveralls.io/builds/5801075 40th build
• travis-ci "PR" build shows code coverage diff
  • https://coveralls.io/builds/5788017

Maybe related to coveralls: lemurheavy/coveralls-public#610

[mattn]

It seems problem already fixed?

[kiambogo]

I'm experiencing the same, across multiple private Go repos. Builds run and report on Codeship with:

#!/bin/bash

goveralls -coverprofile=coverage.out -service=codeship -repotoken $COVERALLS_TOKEN

All repos only show the very first master build, and will only report (notifications) of code coverage on brand new branches.

[gdm85]

Could this be related to a failure at retrieving the git metadata? @dougnukem @kiambogo can you please try with master version of goveralls and enable -debug=true? We should be able to figure this out based on the payload sent to coveralls.io

[nbaztec]

Seems like an intermittent issue on coveralls judging from coveralls-public#610 and python-pillow/Pillow#2060