Skip to content

CI-CD-Other-OS

CI-CD-Other-OS #35

Manually triggered May 19, 2026 09:12
Status Failure
Total duration 20m 37s
Artifacts

main_other_os.yml

on: workflow_dispatch
cache-cleanup
11s
cache-cleanup
Matrix: build-test
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 15 warnings
build-test (r3broot, ubuntu2504, 17, jan24p5, v19.0.1)
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/R3BRoot/R3BRoot/.github/actions/ctest-cdash'. Did you forget to run actions/checkout before running your local action?
build-test (r3broot, ubuntu2504, 17, jan24p5, v19.0.1)
Docker pull failed with exit code 1
build-test (sofia-frs-asy, ubuntu2504, 17, jan24p5, v19.0.1)
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/R3BRoot/R3BRoot/.github/actions/ctest-cdash'. Did you forget to run actions/checkout before running your local action?
build-test (sofia-frs-asy, ubuntu2504, 17, jan24p5, v19.0.1)
Docker pull failed with exit code 1
build-test (glad-tpc, ubuntu2504, 17, jan24p5, v19.0.1)
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/R3BRoot/R3BRoot/.github/actions/ctest-cdash'. Did you forget to run actions/checkout before running your local action?
build-test (glad-tpc, ubuntu2504, 17, jan24p5, v19.0.1)
Docker pull failed with exit code 1
build-test (glad-tpc, ubuntu2604, 17, jan24p6, v19.0.1)
Process completed with exit code 255.
build-test (glad-tpc, ubuntu2604, 17, jan24p6, v19.0.1)
Process completed with exit code 1.
build-test (r3broot, ubuntu2604, 17, jan24p6, v19.0.1)
Process completed with exit code 255.
build-test (r3broot, ubuntu2604, 17, jan24p6, v19.0.1)
Process completed with exit code 1.
build-test (sofia-frs-asy, ubuntu2604, 17, jan24p6, v19.0.1)
Process completed with exit code 255.
build-test (sofia-frs-asy, ubuntu2604, 17, jan24p6, v19.0.1)
Process completed with exit code 1.
build-test (r3broot, ubuntu2504, 17, jan24p5, v19.0.1)
Docker pull failed with exit code 1, back off 3.496 seconds before retry.
build-test (r3broot, ubuntu2504, 17, jan24p5, v19.0.1)
Docker pull failed with exit code 1, back off 4.237 seconds before retry.
build-test (sofia-frs-asy, ubuntu2504, 17, jan24p5, v19.0.1)
Docker pull failed with exit code 1, back off 7.987 seconds before retry.
build-test (sofia-frs-asy, ubuntu2504, 17, jan24p5, v19.0.1)
Docker pull failed with exit code 1, back off 4.039 seconds before retry.
build-test (glad-tpc, ubuntu2504, 17, jan24p5, v19.0.1)
Docker pull failed with exit code 1, back off 2.37 seconds before retry.
build-test (glad-tpc, ubuntu2504, 17, jan24p5, v19.0.1)
Docker pull failed with exit code 1, back off 8.982 seconds before retry.
build-test (glad-tpc, ubuntu2604, 17, jan24p6, v19.0.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-test (r3broot, ubuntu2604, 17, jan24p6, v19.0.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-test (sofia-frs-asy, ubuntu2604, 17, jan24p6, v19.0.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-test (r3broot, ubuntu2504, 17, jan24p5, v18.8.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-test (glad-tpc, ubuntu2504, 17, jan24p5, v18.8.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-test (r3broot, ubuntu2404, 17, jan24p5, v18.8.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-test (glad-tpc, ubuntu2404, 17, jan24p5, v18.8.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-test (sofia-frs-asy, ubuntu2504, 17, jan24p5, v18.8.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-test (sofia-frs-asy, ubuntu2404, 17, jan24p5, v18.8.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/