Skip to content
Ansible

test #434

Sign in to view logs

test

test #434

Triggered via push November 16, 2023 16:01
@jeffreyc-splunkjeffreyc-splunk
pushed 2918970
ansible-new-zeroconfig-test
Status Failure
Total duration 1h 8m 56s
Artifacts –

ansible.yml

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

Annotations

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