Skip to content

Support JDK 26

Support JDK 26 #3522

Triggered via pull request March 19, 2026 00:14
Status Failure
Total duration 33m 54s
Artifacts 9

continuous-integration.yml

on: pull_request
Matrix: build_gradle
Upload event file
3s
Upload event file
Generate latest docs
Generate latest docs
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 9 warnings, and 3 notices
JDK 25 on ubuntu-latest
The process '/usr/bin/xvfb-run' failed with exit code 1
JDK 21 on ubuntu-latest
The process '/usr/bin/xvfb-run' failed with exit code 1
JDK 11 on ubuntu-latest
The process '/usr/bin/xvfb-run' failed with exit code 1
JDK 17 on ubuntu-latest
The process '/usr/bin/xvfb-run' failed with exit code 1
JDK 17 on windows-latest
The process 'D:\a\WALA\WALA\gradlew.bat' failed with exit code 1
JDK 17 on macos-14
The process '/Users/runner/work/WALA/WALA/gradlew' failed with exit code 1
JDK 17 on macos-latest
The process '/Users/runner/work/WALA/WALA/gradlew' failed with exit code 1
Upload event file
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
JDK 25 on ubuntu-latest
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/upload-artifact@v4, GabrielBB/xvfb-action@v1, gradle/actions/setup-gradle@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/
JDK 26 on ubuntu-latest
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/upload-artifact@v4, GabrielBB/xvfb-action@v1, gradle/actions/setup-gradle@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/
JDK 21 on ubuntu-latest
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/upload-artifact@v4, GabrielBB/xvfb-action@v1, gradle/actions/setup-gradle@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/
JDK 11 on ubuntu-latest
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/upload-artifact@v4, GabrielBB/xvfb-action@v1, gradle/actions/setup-gradle@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/
JDK 17 on ubuntu-latest
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/upload-artifact@v4, GabrielBB/xvfb-action@v1, gradle/actions/setup-gradle@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/
JDK 17 on windows-latest
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/upload-artifact@v4, GabrielBB/xvfb-action@v1, gradle/actions/setup-gradle@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/
JDK 17 on macos-14
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/upload-artifact@v4, GabrielBB/xvfb-action@v1, gradle/actions/setup-gradle@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/
JDK 17 on macos-latest
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/upload-artifact@v4, GabrielBB/xvfb-action@v1, gradle/actions/setup-gradle@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/
19 skipped tests found
There are 19 skipped tests, see "Raw output" for the full list of skipped tests.
800 tests found (test 1 to 753)
There are 800 tests, see "Raw output" for the list of tests 1 to 753.
800 tests found (test 754 to 800)
There are 800 tests, see "Raw output" for the list of tests 754 to 800.

Artifacts

Produced during runtime
Name Size Digest
Event file
3.56 KB
sha256:25a1874746464bbca8c10b350b4a56c758c020cafe34fe7224ffa1e9baa3b268
Test results for JDK 11 on ubuntu-latest
651 KB
sha256:eb2a1e24e6cda14f1aacdfa419fba1217e812e2e958e7e98431370eb600614f9
Test results for JDK 17 on macos-14
705 KB
sha256:5433b988a127421f3ecca5d62ec6d83391c9eef204bd37d1e7b6179cbe4706c4
Test results for JDK 17 on macos-latest
706 KB
sha256:6f4eccdfe7c90301cc28152b8f88049985f33f35f33360262476cd53da9dc542
Test results for JDK 17 on ubuntu-latest
713 KB
sha256:999c859a44b130c47e2cac13bcb6a704c55f8a7367ae202568d4f7898140589f
Test results for JDK 17 on windows-latest
424 KB
sha256:63f2fe7db0f3e982a97062b4c788d8e33fe3767f2a30c6248096809f6a0c3084
Test results for JDK 21 on ubuntu-latest
414 KB
sha256:2b6b491b05c162e5d75a26350b38c21d8567028898630b646ed23e3df0fe7165
Test results for JDK 25 on ubuntu-latest
401 KB
sha256:04a21ad896353f2b67266c5ecb6531cbf730a81e6e29da9419764037b5b305cf
Test results for JDK 26 on ubuntu-latest
1.35 MB
sha256:0080becc7fa788133b5773c6e3fa0673213d457276dd0fb3d4fd3097ac8e3481