Skip to content

Add support for JST enum extension #773

Add support for JST enum extension

Add support for JST enum extension #773

Triggered via pull request April 6, 2026 03:42
Status Failure
Total duration 15m 23s
Artifacts 1

build-prs.yml

on: pull_request
Matrix: test-project
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 17 warnings
Build / build
Process completed with exit code 1.
Test testproject on ubuntu-latest (no recomp)
net/minecraft/world/level/storage/LevelStorageSource$LevelStorageAccess$1
Test testproject on ubuntu-latest (no recomp)
net/minecraft/world/level/storage/LevelStorageSource$LevelStorageAccess$1
Test testproject on windows-latest (no recomp)
net/minecraft/world/level/storage/LevelStorageSource$LevelStorageAccess$1
Test testproject on windows-latest (no recomp)
net/minecraft/world/level/storage/LevelStorageSource$LevelStorageAccess$1
Test testproject on ubuntu-latest (recomp)
net/minecraft/world/level/storage/LevelStorageSource$LevelStorageAccess$1
Test testproject on ubuntu-latest (recomp)
net/minecraft/world/level/storage/LevelStorageSource$LevelStorageAccess$1
Test testproject on windows-latest (recomp)
net/minecraft/world/level/storage/LevelStorageSource$LevelStorageAccess$1
Test testproject on windows-latest (recomp)
net/minecraft/world/level/storage/LevelStorageSource$LevelStorageAccess$1
Build / build
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, gradle/actions/setup-gradle@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/
Test legacytest on ubuntu-latest (no recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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/
Test legacytest on ubuntu-latest (no recomp)
Failed to restore gradle-home-v1|Linux|test-project[4f83567ab5d9ed5f2d42cd754d2ce41f]-058054ac17d9776e71c27f7351267aa229bf1e56: Error: Cache service responded with 400
Test testproject on ubuntu-latest (no recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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/
Test testproject on ubuntu-latest (no recomp)
Failed to restore gradle-home-v1|Linux|test-project[e29df6d0aa509f25b2d5bf2d3d960b21]-058054ac17d9776e71c27f7351267aa229bf1e56: Error: Cache service responded with 400
Test testproject on windows-latest (no recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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/
Test testproject on windows-latest (no recomp)
Failed to restore gradle-home-v1|Windows|test-project[2748f45af103653aaa2766d65b60993f]-058054ac17d9776e71c27f7351267aa229bf1e56: Error: Cache service responded with 400
Test legacytest on ubuntu-latest (recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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/
Test legacytest on ubuntu-latest (recomp)
Failed to restore gradle-home-v1|Linux|test-project[40e433df232248ad1667e88840caf8c1]-058054ac17d9776e71c27f7351267aa229bf1e56: Error: Cache service responded with 400
Test legacytest on windows-latest (no recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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/
Test legacytest on windows-latest (no recomp)
Failed to restore gradle-home-v1|Windows|test-project[c5ca0cad6ac1314375b83a31652d0c62]-058054ac17d9776e71c27f7351267aa229bf1e56: Error: Cache service responded with 400
Test testproject on ubuntu-latest (recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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/
Test testproject on ubuntu-latest (recomp)
Failed to restore gradle-home-v1|Linux|test-project[2ad46fe45b69ee45d2c95e9fb1a04a4b]-058054ac17d9776e71c27f7351267aa229bf1e56: Error: Cache service responded with 400
Test testproject on windows-latest (recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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/
Test testproject on windows-latest (recomp)
Failed to restore gradle-home-v1|Windows|test-project[3567a86f426703062338d8edf356d2e2]-058054ac17d9776e71c27f7351267aa229bf1e56: Error: Cache service responded with 400
Test legacytest on windows-latest (recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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/
Test legacytest on windows-latest (recomp)
Failed to restore gradle-home-v1|Windows|test-project[ac838623dac1c799d4bf306de598e5f7]-058054ac17d9776e71c27f7351267aa229bf1e56: Error: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
reports
31.4 KB
sha256:c9d1142049a92a7352cb3452f6fee27021add20f113a57c09e1b84edd641249d