> 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.
Sounds good, GitHub Actions CI looks like it's been working smoothly. Since you introduced it, I haven't encountered any issues in my own PRs or ones that I've reviewed. > 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. Thanks for the advice! I figured this would be the best option in this situation, but since I wasn't sure about how exactly the agents worked, it seemed like a good idea to ask first. On Sat, Feb 1, 2020 at 6:27 AM Steve Dower <steve.do...@python.org> wrote: > 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 > > > > Build: > > > https://dev.azure.com/Python/cpython/_build/results?buildId=57319&view=results > > > > 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.) > > Cheers, > Steve >
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/WANEWGWPZKN2KZGRWSC55DEF7RHRMQ4X/ Code of Conduct: http://python.org/psf/codeofconduct/
