Skip to content
Ansible

ansible: Support new zero config #427

Sign in to view logs

ansible: Support new zero config

ansible: Support new zero config #427

Triggered via pull request November 8, 2023 19:23
@jeffreyc-splunkjeffreyc-splunk
synchronize #3901
ansible-new-zeroconfig
Status Failure
Total duration 1h 15m 19s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ansible.yml

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

Annotations

36 errors
Windows Test (ansible~=6.0, 2016, default)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2016, with_instrumentation)
Process completed with exit code 1.
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, 2019, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2019, default)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2019, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2022, custom_vars)
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, default)
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, 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~=7.0, 2019, default)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2016, 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~=6.0, 2019, 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~=2.10.0, 2022, default)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2022, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2022, default)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2022, default)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2022, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2019, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=7.0, 2019, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2019, default)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
Windows Test (ansible~=6.0, 2012, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2022, with_instrumentation)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
Windows Test (ansible~=2.10.0, 2012, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2012, 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, 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, default)
Process completed with exit code 1.