DavidSpickett wrote: > The self-hosted runner lost communication with the server. Verify the machine > is running and has a healthy network connection. Anything in your workflow > that terminates the runner process, starves it for CPU/Memory, or blocks its > network access can cause this error.
Last time I saw this was building Flang for Compiler Explorer. In that case it was the build using up all the RAM. I can't see the previous logs anymore but if it happens again maybe the last few files ninja prints would be a clue. If Flang is not enabled then it could be CPU use. If you have seen a lot of time based tests time out that's another sign of that. For example lit's timeout and cancellation tests. https://github.com/llvm/llvm-project/pull/163161 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
