On 01Feb2020 1840, Kyle Stanley wrote:
In a recent PR (https://github.com/python/cpython/pull/18057), I received the following error message in the Azure Pipelines build results:
##[error]We stopped hearing from agent Azure Pipelines 5. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610
Is there something on our end we can do to bring the agent back online, or should I simply wait a while and then try to restart the PR checks? Normally I'd avoid doing that, but in this case it's entirely unrelated to the PR.
I think we're at the point where it's probably okay to disable Azure Pipelines as a required check and replace it with the GitHub Actions checks.
But ignoring that for now, I think it's probably best to re-run CI (close/reopen). Just in case the change did actually cause a problem that may only show up on that particular configuration. The agent isn't actually within our control, so it'll be recreated automatically.
(FWIW, the two failing buildbots on the PR are unsupported for 3.9, but haven't been disabled yet.)