API responding with 500 (Build processing error)

[mfittko]

node client throwing following error message since about 8:15 UTC;
{"message":"Build processing error.","error":true,"url":""}

Web page (https://coveralls.io/) also returning with error 500.

Nothing reported on https://status.coveralls.io/

[pheanex]

I've pinged support@coveralls.io also via mail

[harshal-moneylion]

+1 we are also facing the same since ~ 8:00 UTC;

[cheekytinker]

Same issue and also 500 error trying to login via github integration

[EmmaB]

+1 with thanks for looking in to it! Ours is failing via our GitHub Actions integration.

[mfittko]

hope this is soon tackled, our CI pipelines are blocked and we cannot merge to master since more than 3 hours now.

[GeorgiStavrev]

+1 We're also facing this issue, currently having some PRs blocked by this issue, unless we remove the coveralls step from the workflows.

[MarciglianoIT]

I do not think more pressure will make the work faster. But a feedback that you are working on it would be great!

[browniebroke]

In the meantime, we've made the coveralls steps optional

- coveralls
+ coveralls || echo 'Failed to submit coverage report'

[dtieber]

Same issue here. Would be great to get at least some updates on what's happening.

[damjankuznar]

Same here...

[afinetooth]

Thanks @mfittko et. al. We're looking into it.

[andy-maier]

At this point (6h after the site was down), the operational status page still shows all systems as operational... It would be good if such a status would be more reliable.

Anyway, thanks for looking into the issue!

[j0k3r]

@andy-maier at least, the chart speaks for itself

[thomaspoignant]

The status page is updated

[afinetooth]

We are operational again. Monitoring.

Our RDS instance failed to auto-scale, so we've done it manually and are watching for further issues.

[mfittko]

Yay, master branch is green again, thanks for the fix. Hope it's not coming back 🤞

[afinetooth]

It shouldn't. Thanks for your patience.

Our standard notifications did not make it out of EC2 console for some reason. We will add enhanced monitoring this week to avoid future incidents.

Thanks for your patience, all.