Skip to content

Run test suite on windows during CI #23037

Run test suite on windows during CI

Run test suite on windows during CI #23037

Triggered via pull request September 3, 2024 22:45
Status Failure
Total duration 1h 2m 18s
Artifacts

test_suite_windows.yml

on: pull_request
Matrix: build
Matrix: webots-build
Matrix: test-suite
Matrix: delete-artifacts
Fit to window
Zoom out
Zoom in

Annotations

1 error, 15 warnings, and 12 notices
test-suite (windows-2019)
Process completed with exit code 41.
build (windows-2019)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-suite (windows-2019)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
test-suite (windows-2019)
No public SSH keys found for brettle; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
delete-artifacts (windows-2019)
The following actions uses node12 which is deprecated and will be forced to run on node16: geekyeggo/delete-artifact@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
delete-artifacts (windows-2019)
The following actions use a deprecated Node.js version and will be forced to run on node20: geekyeggo/delete-artifact@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-suite (windows-2019)
Web shell: https://tmate.io/t/cR29bY4S9auKFP4yNLs5g9M4x
test-suite (windows-2019)
test-suite (windows-2019)
Web shell: https://tmate.io/t/cR29bY4S9auKFP4yNLs5g9M4x
test-suite (windows-2019)
test-suite (windows-2019)
Web shell: https://tmate.io/t/cR29bY4S9auKFP4yNLs5g9M4x
test-suite (windows-2019)
test-suite (windows-2019)
Web shell: https://tmate.io/t/cR29bY4S9auKFP4yNLs5g9M4x
test-suite (windows-2019)
test-suite (windows-2019)
Web shell: https://tmate.io/t/cR29bY4S9auKFP4yNLs5g9M4x
test-suite (windows-2019)
test-suite (windows-2019)
Web shell: https://tmate.io/t/cR29bY4S9auKFP4yNLs5g9M4x
test-suite (windows-2019)