This incident has been resolved and has been monitored successfully for several hours.
If you think some of your builds were affected by this issue, send us your Coveralls Repo URL to email@example.com and we'll investigate whether we can re-process the builds for you, or if you will need to re-send them.
If you absolutely need a missing build in your build history, the solution is to go to CI and re-run the build in question. That should re-send coverage data to coveralls and place it in your history in a chronologically correct manner. If this isn't happening for you, let us know at firstname.lastname@example.org.
Apologies for the inconvenience around this issue. We appreciate your patience.
Posted Sep 16, 2022 - 17:48 PDT
We have deployed a fix that we expect to resolve this issue for all future builds.
We are still reaching out to repo owners who let us know they may have been affected.
We hope to re-enqueue all missing builds and have them appear by EOD today (Fri, Sep 16).
Again, if you think you were affected, send us your Coveralls Repo URL to email@example.com and we'll make sure your builds get re-processed.
Posted Sep 16, 2022 - 12:52 PDT
We believe we have identified the root cause of this issue and a fix is being implemented that we'll deploy in the next ~1-hour.
At this time, we have identified five (5) affected repos. Missing jobs for those repos will be re-enqueued as soon as the fix is deployed. We will notify each repo owner once this is done.
Again, if you think you may have been affected, send us your Coveralls Repo URL to firstname.lastname@example.org, and we'll ensure your missing builds are re-processed.
Posted Sep 16, 2022 - 09:44 PDT
We've had reports today that some repos have had builds go missing.
The original symptom for these users was that they stopped receiving PR Comments, or Status Updates, at Github; but, looking further into why, we discovered that most of their coverage reports since Sep 13 started builds that never completed.
Our engineers are investigating.
If you think you're affected, please send the Coveralls Repo URL(s) for your affected repo(s) to email@example.com.