"Nothing to report" error

[marvinhagemeister]

We're getting a Nothing to report error on a PR in the Preact repo and we can't figure out why.

  v0.6.15

🔍 Detected coverage file: coverage/lcov.info
🚨 Nothing to report

CI logs https://github.com/preactjs/preact/actions/runs/13282373942/job/37083337231?pr=4652

[marvinhagemeister]

Looks like this was caused by generating an empty coverage report. It was an issue on our side, but leaving this open because the error message should mention that.

[afinetooth]

hi @marvinhagemeister

Thank you for reporting your issue.

We have identified it as being related to the incident we are currently working on here:
https://status.coveralls.io/

You can subscribe to updates there, or I will get back to you with an update here as soon as I have one.

Apologies for the inconvenience.

[afinetooth]

@marvinhagemeister et. al.,

Status:
Wanted to let you know that we are in maintenance mode this morning (US PST timezone):
https://status.coveralls.io/

Apologies for the inconvenience. Please track progress at the URL above, but I will continue updating here (with some degree of lag.)

Workarounds:
To keep Coveralls API failures from failing your CI builds or holding up your PRs, we suggest switching the "fail on error" setting of your Coveralls integration, if available. These settings are documented for each of our Official Integrations, here.

Background:

• We were unable to complete our attempt to clear all backlogged background jobs last night after hitting database connection limits caused by blocking autovacuum operations on three of our biggest tables.
• As progress stalled, we were forced to switch Coveralls to read-only mode and perform manual full vacuums on each of those tables.
• Since those operations will themselves take many hours each, we are working around that by creating an extended schema. We will revert from maintenance mode as soon as we finish.

Thanks again for your patience as we work to get this resolved asap.