GitHub Actions Failing from Last Night: MariaDB via Docker has "Gone Away" #26550
-
Hello all! We’re absolutely stumped trying to figure out why our project’s GitHub Actions builds have stopped working as of a scheduled action run that we have set up to run at 2AM UTC every Sunday. Nothing at all code-wise changed between our last successful build and the first failing build, but every build subsequent to that one throughout the day today has failed for the same reasons. To summarize our setup, we run functional tests by briefly spinning up a set of dependencies via Docker Compose. One of these dependencies is MariaDB, which has suddenly stopped accepting connections as of this morning. On the connecting side, the following error occurs:
On the database, the following error appears with each connection attempt:
We’ve checked every other portion of our setup and can confirm that there are NO changes that were made to:
However, the exact version of the GitHub Actions virtual environment ( Basically, our entire workflow just stopped working out of the blue and we have absolutely no idea what changed to trigger it, so we’re hoping perhaps we’re not the only ones having issues right now and this is somehow a problem with GitHub Actions having pushed some minor changes up this weekend that broke things. If anyone has any feedback they can provide on this, it would be much appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Update: It turns out this wasn’t caused by GitHub Actions in particular, but the actual story is kind of nuts, so I figured I’d post it here for posterity’s sake.
Simply removing the “apt-get upgrade” fixed it. Yeesh. |
Beta Was this translation helpful? Give feedback.
Update: It turns out this wasn’t caused by GitHub Actions in particular, but the actual story is kind of nuts, so I figured I’d post it here for posterity’s sake.