Skip to content

Merge main into develop (#5737) #1025

Merge main into develop (#5737)

Merge main into develop (#5737) #1025

Triggered via push April 9, 2026 16:27
Status Failure
Total duration 50m 21s
Artifacts
frontend-unit-tests
27s
frontend-unit-tests
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

22 errors and 3 warnings
build (25)
Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run
build (25)
Connection is closed
build (25)
java.lang.InterruptedException
build (25)
java.lang.InterruptedException
build (25)
Connection has been closed
build (25)
java.lang.InterruptedException
build (25)
java.lang.InterruptedException
build (25)
java.lang.InterruptedException
build (25)
Connection has been closed
build (25)
java.lang.InterruptedException
build (25)
java.lang.InterruptedException
build (21)
The strategy configuration was canceled because "build._25" failed
build (21)
java.lang.InterruptedException
build (21)
java.lang.InterruptedException
build (21)
Connection is closed
build (21)
Connection has been closed
build (21)
java.lang.InterruptedException
build (21)
java.lang.InterruptedException
build (21)
Connection has been closed
build (21)
java.lang.InterruptedException
build (21)
java.lang.InterruptedException
build (21)
java.lang.InterruptedException
frontend-unit-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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 (25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/thread-dump-post, actions/cache@v4, actions/checkout@v4, actions/setup-java@v1, scacap/action-surefire-report@v1. 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 (21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/thread-dump-post, actions/cache@v4, actions/checkout@v4, actions/setup-java@v1. 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/