coqbot running well across our repos (thanks to @Théo Zimmermann) but just encountered a different problem. This PR has had a multiple pushes and
coqbot continued to work as normal until the last push:
The actual commit was pushed through to GitLab CI (https://gitlab.com/saltstack-formulas/packages-formula/-/pipelines/245925810) but the reporting back on the PR is now missing. What could we do from our side to re-establish this?
The links I've mentioned here should still show the situation, even if the PR's author pushes another commit and it starts working again.
Hmm, it's finally showed up now, without another commit being pushed. I only noticed when the PR author added another comment to the discussion.
@Imran Iqbal Thanks for the report. I also got a lot of automatic alerts about Heroku memory quota exceeded and unusually long response delays (which could be related to swapping) since yesterday. Unfortunately, I haven't been in front of a computer to investigate them. What surprises me though is that I don't know what changed to provoke this. Did you happen to generalize the use of coqbot very recently in your organization?
I've had no automatic report for more issues like this today. Let me know if you see them again.
@Théo Zimmermann Haven't changed anything at all recently. I got everything set up the last time we spoke and it has been working reliably since then. This was the first time I noticed something amiss. I'll let you know if anything happens again. Thanks for the response.
Thanks for your feedback!
Last updated: May 28 2023 at 18:29 UTC