Closed tscottjendev closed 2 weeks ago
That is very strange... It states: Ready for connections! (which means the container is complete), but never continues... Assuming that this is self-hosted runners?
Shoot me an email on freddyk at microsoft dot com if you want to jump on a call and have a look
AL-Go version
6.0
Describe the issue
CI/CD build run for 6 hours and then is cancelled by GitHub. This only started this week. It appears to "stall" on the creating of the container.
I have included the log for one of these instances. We have 3 that have failed and none have succeeded this week.
We are working on pull requests into a feature branch and the CI/CD into the feature branch fails.
Expected behavior
Our CI/CD builds normally complete in ~30 minutes, would expect similar results now.
Steps to reproduce
Simply start the CI/CD action.
Additional context (logs, screenshots, etc.)
Complete log attached, here is the relevant output from the container creation.
logs_30222690906.zip