No coverage info available after Travis build

lemurheavy / coveralls-public

The public issue tracker for coveralls.io

http://coveralls.io

124 stars 7 forks source link

No coverage info available after Travis build #114

Closed ledestin closed 11 years ago

ledestin commented 11 years ago

Hi,

I seem to have done everything to enable Coveralls for my project, but there's still no info about coverage for my project. https://github.com/ledestin/frugal_timeout

kyledayton commented 11 years ago

I too am having the same issue with http://github.com/kdayton-/planify

Travis is showing that the information is being posted to the Coveralls API, but it still says the coverage is unknown.

ross-p commented 11 years ago

Same issue for me

Github: https://github.com/vube/php-filesystem Travis: https://travis-ci.org/vube/php-filesystem/jobs/9249351 Coveralls: https://coveralls.io/jobs/271327

phpunit completed successfully. build/logs/clover.xml created successfully. coveralls reported that it did post to coveralls.io with a job number that does exist in coveralls.io.

However there is no information on coveralls.io except the job number.

aarellano commented 11 years ago

Same issue here: https://github.com/peepoltv/peepoltv-api

darbula commented 11 years ago

Same issue here.

Github: https://github.com/darbula/pymote Travis: https://travis-ci.org/darbula/pymote/builds/9286057 Coveralls: https://coveralls.io/jobs/274958

Everything seems fine but there is no coverage report.

darbula commented 11 years ago

All right now, it seems like this issue is solved somehow.

ghost commented 11 years ago

Dup of #116

dougwt commented 11 years ago

My travis-ci builds have been showing no info for the past 3 days. https://coveralls.io/r/dougwt/user-stories

nickmerwin commented 11 years ago

Hi all, sorry for the epically late response, we were having some queue processing issues around this time, it looks like everyone's data has processed.

Let me know if anyone is still seeing unprocessed jobs. Thanks!

ledestin commented 11 years ago

My badge is still stuck at an old commit.

nickmerwin commented 11 years ago

hi @ledestin is see that your last build from over a month ago encountered a timeout: https://travis-ci.org/ledestin/frugal_timeout

Could you restart the build from Travis to try again?

ledestin commented 11 years ago

I don't see it changing since I've tried `coveralls push' just recently and it fails with a timeout.

nickmerwin commented 11 years ago

Hm, could it be that your timeout patch is interfering with RestClient?

ledestin commented 11 years ago

Hey, thanks a lot! It was indeed the case.