Skip to content

GH-5711 improve data import speed (also GH-5748) (#5721) #639

GH-5711 improve data import speed (also GH-5748) (#5721)

GH-5711 improve data import speed (also GH-5748) (#5721) #639

Triggered via push April 15, 2026 16:10
Status Success
Total duration 1h 2m 1s
Artifacts

main-status.yml

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

Annotations

20 errors and 3 warnings
build (17)
Connection is 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)
Connection has been closed
build (17)
java.lang.InterruptedException
build (17)
java.lang.InterruptedException
build (17)
java.lang.InterruptedException
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. 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 (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. 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 (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. 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/