Azure Pipelines PR: Unresponsive agent
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.
On 01Feb2020 1840, Kyle Stanley wrote:
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
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.
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.dower@python.org> wrote:
This seems the best thread to follow up on, just had a spurious failure backporting a patch to 3.8 from master: https://dev.azure.com/Python/cpython/_build/results?buildId=57386&view=logs&j=c83831cd-3752-5cc7-2f01-8276919eb334&t=5a421c4a-0933-53d5-26b9-04b36ad165eb <https://dev.azure.com/Python/cpython/_build/results?buildId=57386&view=logs&j=c83831cd-3752-5cc7-2f01-8276919eb334&t=5a421c4a-0933-53d5-26b9-04b36ad165eb> Trying the close/re-open to get CI to re-run... Chris On 01/02/2020 23:20, Kyle Stanley wrote:
Le sam. 1 févr. 2020 à 12:34, Steve Dower <steve.dower@python.org> a écrit :
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.
More and more often, I'm waiting for Azure Pipelines to complete: it's currently the slowest "CI" (made of multiple jobs) on pull requests. But it seems like Azure Pipelines basically re-do the same tests which are already done on GitHub Actions: Windows (32 and 64-bit), macOS, Ubuntu, Docs. GitHub Actions seem better integrated with GitHub. Would it make sense to simply remove Azure Pipelines integration, to only keep GitHub Actions? It would allow to merge PRs faster. Victor -- Night gathers, and now my watch begins. It shall not end until my death.
On 01Feb2020 1840, Kyle Stanley wrote:
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
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.
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.dower@python.org> wrote:
This seems the best thread to follow up on, just had a spurious failure backporting a patch to 3.8 from master: https://dev.azure.com/Python/cpython/_build/results?buildId=57386&view=logs&j=c83831cd-3752-5cc7-2f01-8276919eb334&t=5a421c4a-0933-53d5-26b9-04b36ad165eb <https://dev.azure.com/Python/cpython/_build/results?buildId=57386&view=logs&j=c83831cd-3752-5cc7-2f01-8276919eb334&t=5a421c4a-0933-53d5-26b9-04b36ad165eb> Trying the close/re-open to get CI to re-run... Chris On 01/02/2020 23:20, Kyle Stanley wrote:
Le sam. 1 févr. 2020 à 12:34, Steve Dower <steve.dower@python.org> a écrit :
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.
More and more often, I'm waiting for Azure Pipelines to complete: it's currently the slowest "CI" (made of multiple jobs) on pull requests. But it seems like Azure Pipelines basically re-do the same tests which are already done on GitHub Actions: Windows (32 and 64-bit), macOS, Ubuntu, Docs. GitHub Actions seem better integrated with GitHub. Would it make sense to simply remove Azure Pipelines integration, to only keep GitHub Actions? It would allow to merge PRs faster. Victor -- Night gathers, and now my watch begins. It shall not end until my death.
participants (4)
-
Chris Withers -
Kyle Stanley -
Steve Dower -
Victor Stinner