Missing build data in builds from last week?

What to do

• Check whether you use Coveralls in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1d it lasted.

  Anything that failed between 2024-08-26 19:27 UTC and 2024-08-27 19:37 UTC may need a replay.

• Subscribe to Coveralls's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=coveralls works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Coveralls 2

1. monitoringAug 26, 2024, 7:27 PM UTC

   We've had a couple of reports from customers about builds that were received by the Coveralls API prior to last week's outage (https://status.coveralls.io/incidents/mmg3wsghl3k5), which indicate they may not have been fully processed. This would most likely be due to background jobs responsible for fully processing these builds getting caught up in service failures during our outage and, as a result, potentially, running out of retries and never completing. If you think any of your builds may have been affected this way, we have two suggested remedies: 1) Re-run the build via our API > ReRun Build Webhook - Documented here: https://docs.coveralls.io/api-introduction#rerun-build-webhook, the ReRun Build webhook will re-process any existing build, including a full recalculation of all received coverage report data. Here's how to issue a rerun via the API (just substitute your "Build Number" and Repo Token): curl --location 'http://coveralls.io/rerun_build?build_num= &repo_token= ' \ --header 'Content-Type: application/json' Note that `build_num` can be either the Build Number assigned to your build by your CI service, or the build's commit SHA per GitHub. 2) Reach out to us at support@coveralls.io - We'll be happy to re-run your build for you, or investigate further if rerunning the build doesn't resolve your issue. Thanks to all customers for your patience with us last week.

   provider

2. resolvedAug 27, 2024, 7:37 PM UTC

   Closing this for now. Please try re-running any builds you think may have been affected last week, or reach and we'll be glad to help.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.