Skip to content

Github CI formatter (#5726) #632

Github CI formatter (#5726)

Github CI formatter (#5726) #632

Triggered via push March 23, 2026 18:05
Status Failure
Total duration 54m 29s
Artifacts

main-status.yml

on: push
frontend-unit-tests
23s
frontend-unit-tests
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

22 errors and 3 warnings
build (17)
Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run
build (17)
java.lang.InterruptedException
build (17)
java.lang.InterruptedException
build (17)
java.lang.InterruptedException
build (17)
java.lang.InterruptedException
build (17)
java.lang.InterruptedException
build (17)
java.lang.InterruptedException
build (17)
java.lang.InterruptedException
build (17)
Connection has been closed
build (17)
Connection has been closed
build (17)
Connection has been closed
build (11)
The strategy configuration was canceled because "build._17" failed
build (11)
java.lang.InterruptedException
build (11)
java.lang.InterruptedException
build (11)
java.lang.InterruptedException
build (11)
Connection has been closed
build (11)
java.lang.InterruptedException
build (11)
Connection has been closed
build (11)
java.lang.InterruptedException
build (11)
java.lang.InterruptedException
build (11)
java.lang.InterruptedException
build (11)
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. 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 (17)
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. 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 (11)
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. 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/