Skip to content

Run Java examples #2282

Run Java examples

Run Java examples #2282

Triggered via schedule April 13, 2026 22:52
Status Failure
Total duration 1h 15m 19s
Artifacts 5

java-examples.yml

on: schedule
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 16 warnings
tests (ubuntu, stable)
Final attempt failed. Child_process exited with error code 1
tests (ubuntu, nightly)
Final attempt failed. Child_process exited with error code 1
tests (macos, stable)
Final attempt failed. Child_process exited with error code 1
tests (windows, stable)
Final attempt failed. Child_process exited with error code 1
tests (macos, nightly)
Final attempt failed. Timeout of 2400000ms hit
tests (windows, nightly)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-invision/retry@v3.0.2. 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/
tests (ubuntu, stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-invision/retry@v3.0.2. 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/
tests (ubuntu, stable)
Attempt 2 failed. Reason: Child_process exited with error code 1
tests (ubuntu, stable)
Attempt 1 failed. Reason: Child_process exited with error code 1
tests (ubuntu, nightly)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-invision/retry@v3.0.2. 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/
tests (ubuntu, nightly)
Attempt 2 failed. Reason: Child_process exited with error code 1
tests (ubuntu, nightly)
Attempt 1 failed. Reason: Child_process exited with error code 1
tests (macos, stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-invision/retry@v3.0.2. 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/
tests (macos, stable)
Attempt 2 failed. Reason: Child_process exited with error code 1
tests (macos, stable)
Attempt 1 failed. Reason: Child_process exited with error code 1
tests (windows, stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-invision/retry@v3.0.2. 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/
tests (windows, stable)
Attempt 2 failed. Reason: Child_process exited with error code 1
tests (windows, stable)
Attempt 1 failed. Reason: Child_process exited with error code 1
tests (macos, nightly)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-invision/retry@v3.0.2. 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/
tests (macos, nightly)
Attempt 2 failed. Reason: Child_process exited with error code 1
tests (macos, nightly)
Attempt 1 failed. Reason: Child_process exited with error code 1

Artifacts

Produced during runtime
Name Size Digest
test-report-macos-nightly
418 KB
sha256:07a52b14cd69feae232a697329e5d566bdddfb11447edae9b6b5f8e6dba5d0b0
test-report-macos-stable
411 KB
sha256:46c18ef41bd4b3794d610eee13f59af83dfcdfdc39d5a3e067aa2f2d496dc97d
test-report-ubuntu-nightly
401 KB
sha256:cacbfc1569d24a9bc2d70997a6df16b0f38d60f451b118024961c5bfb8c0f3da
test-report-ubuntu-stable
399 KB
sha256:08ef63cd3f4f4d3e2c7437b3bd91b4068228530c2b08d0598c4a5308521475bd
test-report-windows-stable
417 KB
sha256:a7d7faa82779ea5b48c0a144b76430a0d25b8b14b9a4cd9811947d59eee1ddd3