Skip to content
Ansible

[ansible] Fix test flakiness with Windows #1036

Sign in to view logs

[ansible] Fix test flakiness with Windows

[ansible] Fix test flakiness with Windows #1036

Triggered via pull request May 21, 2025 21:23
@crobert-1crobert-1
synchronize #6222
crobert-1:fix_virtualbox_vagrant
Status Cancelled
Total duration 26m 36s
Artifacts –

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

46 errors
Linux Test (ansible~=10.7.0, centos9)
Process completed with exit code 1.
Linux Test (ansible~=11.6.0, centos9)
Process completed with exit code 1.
Windows Test (ansible~=10.7.0, 2016, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=11.6.0, 2016, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=10.7.0, 2016, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=11.6.0, 2016, default)
Process completed with exit code 1.
Windows Test (ansible~=10.7.0, 2016, default)
Process completed with exit code 1.
Windows Test (ansible~=11.6.0, 2016, custom_vars)
Process completed with exit code 1.
Windows Test (ansible~=11.6.0, 2022, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=11.6.0, 2019, with_instrumentation)
Process completed with exit code 1.
Windows Test (ansible~=11.6.0, 2019, default)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Windows Test (ansible~=11.6.0, 2019, default)
Process completed with exit code 143.
Windows Test (ansible~=10.7.0, 2019, custom_vars)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Windows Test (ansible~=10.7.0, 2019, custom_vars)
Process completed with exit code 143.
Windows Test (ansible~=11.6.0, 2019, custom_vars)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Windows Test (ansible~=11.6.0, 2019, custom_vars)
Process completed with exit code 143.
Windows Test (ansible~=10.7.0, 2019, with_instrumentation)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Windows Test (ansible~=10.7.0, 2019, with_instrumentation)
Process completed with exit code 143.
Windows Test (ansible~=10.7.0, 2019, default)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Windows Test (ansible~=10.7.0, 2019, default)
Process completed with exit code 143.
Windows Test (ansible~=10.7.0, 2022, custom_vars)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Windows Test (ansible~=10.7.0, 2022, custom_vars)
The operation was canceled.
Linux Test (ansible~=10.7.0, debian12)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=10.7.0, debian12)
The operation was canceled.
Windows Test (ansible~=10.7.0, 2022, with_instrumentation)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Windows Test (ansible~=10.7.0, 2022, with_instrumentation)
The operation was canceled.
Linux Test (ansible~=10.7.0, ubuntu2204)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=10.7.0, ubuntu2204)
The operation was canceled.
Linux Test (ansible~=10.7.0, amazonlinux2023)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=10.7.0, amazonlinux2023)
The operation was canceled.
Linux Test (ansible~=11.6.0, debian11)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=11.6.0, debian11)
The operation was canceled.
Linux Test (ansible~=10.7.0, debian11)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=10.7.0, debian11)
The operation was canceled.
Linux Test (ansible~=11.6.0, amazonlinux2023)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=11.6.0, amazonlinux2023)
The operation was canceled.
Windows Test (ansible~=11.6.0, 2022, custom_vars)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Windows Test (ansible~=11.6.0, 2022, custom_vars)
The operation was canceled.
Linux Test (ansible~=11.6.0, ubuntu2204)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=11.6.0, ubuntu2004)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=11.6.0, ubuntu2204)
The operation was canceled.
Linux Test (ansible~=11.6.0, ubuntu2004)
The operation was canceled.
Linux Test (ansible~=10.7.0, ubuntu2004)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=10.7.0, ubuntu2004)
The operation was canceled.
Linux Test (ansible~=11.6.0, debian12)
Canceling since a higher priority waiting request for 'ansible-6222' exists
Linux Test (ansible~=11.6.0, debian12)
The operation was canceled.