Skip to content

GH-5732: fix application specific thread context in federated service… #634

GH-5732: fix application specific thread context in federated service…

GH-5732: fix application specific thread context in federated service… #634

Re-run triggered April 7, 2026 21:54
Status Cancelled
Total duration 52m 19s
Artifacts

main-status.yml

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

Annotations

11 errors and 1 warning
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)
Connection has been closed
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)
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/