Coveralls showing data from another repository?

[Hixie]

The source files listed on https://coveralls.io/github/flutter/flutter have nothing to do with our repo:

The coverage numbers seem accurate, though.

[thanosd]

I'm seeing the same thing. Commits from a totally different repo. Private repo:

https://coveralls.io/github/savvymx/savvyanalysis

[anjin]

Hi!

Make sure you have "service_name: travis-pro" in your .coveralls.yml.

Travis uses non-unique job id's between its free and pro services, so if Coveralls doesn't know that your service-name is travis-pro, it looks up the info for those job ids using the free Travis API -- that's why they will show random commits and builds. Once your ENV var is set to specify travis-pro, the correct info will be pulled from Travis's pro API.

Conversely, no one will be able to see your private commits because the Travis-pro API requires special authentication via your Github OAuth token (whereas Travis free doesn't require any) -- the build ID mix-up can only go one way thankfully.

[thanosd]

Not so fast. ;) I already that have in my config and still seeing the issue.

[thanosd]

Related: shouldn't coveralls be "smart" enough to see this is a different repo and suppress the information?

[Hixie]

I added the line suggested above, and it didn't fix it. If anything it made it worse, I'm not sure the numbers are correct anymore.

[Hixie]

@anjin I think this should be reopened. It makes coveralls useless to us, basically.

[joroshiba]

@Hixie, sorry for the inconvenience, we have identified the cause of this error and are working on getting a patch put together to solve it.

[Hixie]

@bytewalls any news?

[Hixie]

This is still broken. Flutter's coveralls page hasn't shown reasonable data since at least as far back as last April.

[Hixie]

Since this continues to be broken I guess we'll have to stop trying to use coveralls.

[xster]

I think there are 2 separate issues.
https://coveralls.io/builds/21162782 etc are still showing the right per build data we're sending up to https://coveralls.io/api/v1/jobs. It's just not connecting to any metadata at the https://coveralls.io/github/flutter/flutter level.

Behind the scene, what data does coveralls retrieve from various CI's APIs based on service_name? Can we provide everything that coveralls needs in one single post to https://coveralls.io/api/v1/jobs and not depend on any callbacks to any CI service?

But otherwise, the fact that https://coveralls.io/github/flutter/flutter can't list the files in our repo at all seems like a bug since it shouldn't depend on any CIs to show the right data.

[stale]

This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions.

[Hixie]

For what it's worth, we stopped using coveralls because of this issue.

[stale]

This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions.