Skip to content

ansible: Support new zero config #437

ansible: Support new zero config

ansible: Support new zero config #437

Triggered via pull request November 27, 2023 16:43
Status Cancelled
Total duration 47m 42s
Artifacts

ansible.yml

on: pull_request
Push Release Tag
0s
Push Release Tag
Matrix: Linux Test
Matrix: Windows Test
Fit to window
Zoom out
Zoom in

Annotations

37 errors and 3 warnings
Windows Test (ansible~=2.10.0, 2016, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2016, default)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2016, default)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2012, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2012, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2012, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2012, default)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2012, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2016, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2016, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2016, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2016, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2016, default)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2019, with_instrumentation)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
Windows Test (ansible~=2.10.0, 2019, default)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
Windows Test (ansible~=2.10.0, 2019, custom_vars)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
Windows Test (ansible~=7.0, 2022, default)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2022, custom_vars)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
Windows Test (ansible~=2.10.0, 2016, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2019, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2022, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2022, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2019, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2019, default)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2012, default)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2012, default)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2012, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2022, with_instrumentation)
Canceling since a higher priority waiting request for 'ansible-3901' exists
Windows Test (ansible~=2.10.0, 2022, with_instrumentation)
The operation was canceled.
Windows Test (ansible~=2.10.0, 2022, custom_vars)
Canceling since a higher priority waiting request for 'ansible-3901' exists
Windows Test (ansible~=2.10.0, 2022, custom_vars)
The hosted runner: GitHub Actions 53 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Windows Test (ansible~=2.10.0, 2022, default)
Canceling since a higher priority waiting request for 'ansible-3901' exists
Windows Test (ansible~=2.10.0, 2022, default)
The hosted runner: GitHub Actions 52 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Windows Test (ansible~=6.0, 2019, with_instrumentation)
Canceling since a higher priority waiting request for 'ansible-3901' exists
Windows Test (ansible~=6.0, 2019, with_instrumentation)
The hosted runner: GitHub Actions 69 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Windows Test (ansible~=6.0, 2022, default)
Canceling since a higher priority waiting request for 'ansible-3901' exists
Windows Test (ansible~=6.0, 2022, default)
The hosted runner: GitHub Actions 72 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Windows Test (ansible~=6.0, 2022, with_instrumentation)
Received request to deprovision: The request was cancelled by the remote provider.
Windows Test (ansible~=7.0, 2019, default)
Received request to deprovision: The request was cancelled by the remote provider.
Windows Test (ansible~=6.0, 2019, custom_vars)
Received request to deprovision: The request was cancelled by the remote provider.