afinetooth
commented
3 years ago Hi @estebanzimanyi, it's almost certain your issue was caused by general performance issues we've been experiencing for the past 24-36 hrs.
You can track status here: https://status.coveralls.io/
For some time, the API was intermittently unavailable, returning 5XX errors. At this point, the API is operational so you can retry your build(s). Please just be aware that we're still experiencing degraded performance with the Web UI so your build pages will not fully render for some time. The background jobs that perform your aggregate calculations and render some interactive elements on each build page are backed up in heavy traffic.
You can rest assured that any jobs accepted by the API will be processed in time without any further action required from you. We are doing our best to clear the traffic and get back to normal performance by this afternoon.
Related:
estebanzimanyi
There could be a problem in Coveralls since we receive the error
when using the standard
lcovtool for filtering directories on which the coverage information are collected. Compare the commit https://github.com/MobilityDB/MobilityDB/commit/2ef7f77335c25c4025884dc6679fa94fb9a725ab which solved the issue in the previous commit https://github.com/MobilityDB/MobilityDB/runs/3465656814 Basically, the output of the following command works with Coverallsbut the output of following commands
send the above error.