Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3.5.0. 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/

This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.

Failed to restore gradle-home-v1|Linux|metrics[0afb79acc8a8328fb6bd71072249636c]-82f9c72f310770535afd273901da767936a9d372: Error: Cache service responded with 400

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3.5.0. 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/

This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.

Failed to restore gradle-home-v1|macOS|metrics[687cd5d435aca06a1b28f179fdbb4c05]-82f9c72f310770535afd273901da767936a9d372: Error: Cache service responded with 400

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3.5.0. 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/

This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.

Failed to restore gradle-home-v1|Linux|metrics[419c195f369f6f7487088abdf4d1d9d2]-82f9c72f310770535afd273901da767936a9d372: Error: Cache service responded with 400

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3.5.0. 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/

This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.

Failed to restore gradle-home-v1|macOS|metrics[3fbefd17e400d340bb7f2ba2e56758ef]-82f9c72f310770535afd273901da767936a9d372: Error: Cache service responded with 400

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 1s Peak memory utilization: 8.2 GB (47.83% of 17 GB) at 90s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 1s Peak memory utilization: 7.5 GB (43.41% of 17 GB) at 140s

Peak CPU utilization: 0.74 cores (4.60% of 16.00) at 9s Peak memory utilization: 269 MB (0.53% of 50 GB) at 12s

Peak CPU utilization: 0.64 cores (4.00% of 16.00) at 10s Peak memory utilization: 304 MB (0.60% of 50 GB) at 15s

Peak CPU utilization: 0.65 cores (4.06% of 16.00) at 10s Peak memory utilization: 244 MB (0.48% of 50 GB) at 15s

Peak CPU utilization: 0.87 cores (21.87% of 4.00) at 10s Peak memory utilization: 8.1 GB (46.99% of 17 GB) at 9s

Peak CPU utilization: 1.29 cores (32.32% of 4.00) at 4s Peak memory utilization: 7.8 GB (45.45% of 17 GB) at 15s

Peak CPU utilization: 1.23 cores (30.81% of 4.00) at 11s Peak memory utilization: 7.1 GB (41.56% of 17 GB) at 9s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 1s Peak memory utilization: 7.4 GB (43.02% of 17 GB) at 130s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 1s Peak memory utilization: 7.4 GB (42.86% of 17 GB) at 21s

Peak CPU utilization: 0.65 cores (4.04% of 16.00) at 9s Peak memory utilization: 292 MB (0.58% of 50 GB) at 13s

Peak CPU utilization: 0.69 cores (4.34% of 16.00) at 14s Peak memory utilization: 314 MB (0.62% of 50 GB) at 14s

Peak CPU utilization: 3.05 cores (76.31% of 4.00) at 7s Peak memory utilization: 7.4 GB (43.15% of 17 GB) at 11s

Peak CPU utilization: 9.97 cores (62.32% of 16.00) at 330s Peak memory utilization: 8.9 GB (17.65% of 50 GB) at 310s

Peak CPU utilization: 3.96 cores (98.97% of 4.00) at 70s Peak memory utilization: 9.6 GB (55.82% of 17 GB) at 200s

Peak CPU utilization: 9.49 cores (59.28% of 16.00) at 410s Peak memory utilization: 8.4 GB (16.58% of 50 GB) at 430s