Is Coveralls Down?

Resolved Minor [Re-Opened] Github status updates failing intermittently

Re-opening this incident from yesterday, THU, APR 14, since we are receiving more reports this morning: > We are getting reports of Github status updates not arriving at Github for repos that have been fine in this regard for a long time. We are noticing an uptick in background job failures responsible for these status updates. In most cases, these failures resolve immediately by re-trying them. But some fail a few times before succeeding. We suspect there's an issue with the Github API (though not according to https://www.githubstatus.com/), or an isolated issue between coveralls.io and github.com, that's resulting in behavior like rate limiting. There is no known basis for actual rate limiting, but this is the effect. > > Please know that any failing status updates will be retried in exponential back-off fashion (so they should eventually succeed) and that we are monitoring closely and will take any action we can to improve things.

Resolved Minor Github status updates failing intermittently

We are getting reports of Github status updates not arriving at Github for repos that have been fine in this regard for a long time. We are noticing an uptick in background job failures responsible for these status updates. In most cases, these failures resolve immediately by re-trying them. But some fail a few times before succeeding. We suspect there's an issue with the Github API (though not according to https://www.githubstatus.com/), or an isolated issue between coveralls.io and github.com, that's resulting in behavior like rate limiting. There is no known basis for actual rate limiting, but this is the effect. Please know that any failing status updates will be retried in exponential back-off fashion (so they should eventually succeed) and that we are monitoring closely and will take any action we can to improve things.

Resolved Minor Slow performance

We have reports of slow build times for some repos over the last 48-hrs. We are taking measures to clear backed up queues holding background jobs that are waiting to process and complete existing builds. Will post updates here. If you suspect your repo was paused due to excessive use (more than 200- jobs), you can reach out to [email protected] and we can confirm. All paused repos will be un-paused by end-of-day, once background queues are 80% cleared.

Resolved Minor Slower than normal build times due to heavy traffic

The issue has been identified and a fix is being implemented.

Resolved Minor Slow performance due to high traffic

Some users are experiencing slow build times due to traffic on shared resources. We may pause some repos with unusually high use of shared processing resources and temporarily increase processing resources to help clear background queues. If you are experiencing slow PR status checks or comments, or receiving 0% coverage and/or a "DataTables" error on your build page for a recent build, please know that these are all effects of slow performance (delayed processing) and that we are attempting to address these issues with our current efforts. Rest assured that if you received a 200 success response in your CI build log, your job(s) will eventually complete, your build page will fully render and you will receive PR status checks and comments.