Skip to content

pin virtualbox and retry molecule if VM fails to start #454

pin virtualbox and retry molecule if VM fails to start

pin virtualbox and retry molecule if VM fails to start #454

Triggered via push November 29, 2023 15:25
Status Cancelled
Total duration 27m 9s
Artifacts

ansible.yml

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

Annotations

58 errors and 7 warnings
Windows Test (ansible~=2.10.0, 2012, with_instrumentation)
Process completed with exit code 2.
Windows Test (ansible~=7.0, 2016, custom_vars)
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, 2016, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2016, default)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2016, custom_vars)
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, with_instrumentation)
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~=6.0, 2019, 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, 2022, default)
Process completed with exit code 1.
Windows Test (ansible~=2.10.0, 2022, default)
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, 2022, default)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2019, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2022, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=6.0, 2022, with_instrumentation)
Process completed with exit code 1.
Linux Test (ansible~=6.0, ubuntu1804)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Linux Test (ansible~=2.10.0, debian9)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Linux Test (ansible~=2.10.0, centos7)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Linux Test (ansible~=2.10.0, centos7)
The operation was canceled.
Linux Test (ansible~=2.10.0, centos8)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Linux Test (ansible~=2.10.0, centos8)
The operation was canceled.
Linux Test (ansible~=7.0, centos8)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Linux Test (ansible~=7.0, centos8)
The operation was canceled.
Linux Test (ansible~=6.0, centos8)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Linux Test (ansible~=6.0, centos8)
The operation was canceled.
Windows Test (ansible~=2.10.0, 2012, default)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=2.10.0, 2012, default)
The operation was canceled.
Windows Test (ansible~=7.0, 2022, custom_vars)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=7.0, 2022, custom_vars)
The operation was canceled.
Linux Test (ansible~=2.10.0, ubuntu1804)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Linux Test (ansible~=2.10.0, ubuntu1804)
The operation was canceled.
Windows Test (ansible~=7.0, 2012, default)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=7.0, 2012, default)
The operation was canceled.
Windows Test (ansible~=6.0, 2012, default)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=6.0, 2012, default)
The operation was canceled.
Windows Test (ansible~=2.10.0, 2022, with_instrumentation)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=2.10.0, 2022, with_instrumentation)
The operation was canceled.
Windows Test (ansible~=7.0, 2012, custom_vars)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=7.0, 2012, custom_vars)
The operation was canceled.
Windows Test (ansible~=6.0, 2012, with_instrumentation)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=6.0, 2012, with_instrumentation)
The operation was canceled.
Windows Test (ansible~=2.10.0, 2012, custom_vars)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=2.10.0, 2012, custom_vars)
The operation was canceled.
Windows Test (ansible~=7.0, 2012, with_instrumentation)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=7.0, 2012, with_instrumentation)
The operation was canceled.
Windows Test (ansible~=2.10.0, 2019, with_instrumentation)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=2.10.0, 2019, with_instrumentation)
The operation was canceled.
Windows Test (ansible~=6.0, 2012, custom_vars)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=2.10.0, 2019, custom_vars)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=7.0, 2019, default)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=6.0, 2019, custom_vars)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=7.0, 2019, custom_vars)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=7.0, 2019, with_instrumentation)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=7.0, 2022, with_instrumentation)
Canceling since a higher priority waiting request for 'ansible-refs/heads/ansible-new-zeroconfig-test' exists
Windows Test (ansible~=6.0, 2012, custom_vars)
Runner GitHub Actions 25 did not respond to a cancelation request with 00:05:00.
Windows Test (ansible~=2.10.0, 2019, custom_vars)
Runner GitHub Actions 18 did not respond to a cancelation request with 00:05:00.
Windows Test (ansible~=7.0, 2019, default)
Runner GitHub Actions 53 did not respond to a cancelation request with 00:05:00.
Windows Test (ansible~=6.0, 2019, custom_vars)
Runner GitHub Actions 33 did not respond to a cancelation request with 00:05:00.
Windows Test (ansible~=7.0, 2019, custom_vars)
Runner GitHub Actions 47 did not respond to a cancelation request with 00:05:00.
Windows Test (ansible~=7.0, 2019, with_instrumentation)
Runner GitHub Actions 52 did not respond to a cancelation request with 00:05:00.
Windows Test (ansible~=7.0, 2022, with_instrumentation)
Runner GitHub Actions 59 did not respond to a cancelation request with 00:05:00.