Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.

No files were found with the provided path: samples/react-native/android/*.log. No artifacts will be uploaded.

Failed to restore gradle-home-v1|Linux|build-android[76945e00d18b094858850ca2f6755e43]-825a670c4dae28d89d8991a3d195cf1c1f93a151: 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: dniHze/maestro-test-action@bda8a93211c86d0a05b7a4597c5ad134566fbde4, futureware-tech/simulator-action@e89aa8f93d3aec35083ff49d2854d07f7186f7f5. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.

No files were found with the provided path: samples/react-native/android/*.log. No artifacts will be uploaded.

Failed to restore gradle-home-v1|Linux|build-android[26c3db2f35373b3d09e85a212763dd50]-825a670c4dae28d89d8991a3d195cf1c1f93a151: 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: dniHze/maestro-test-action@bda8a93211c86d0a05b7a4597c5ad134566fbde4. 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/

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 49s Peak memory utilization: 9.6 GB (56.15% of 17 GB) at 310s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 54s Peak memory utilization: 9.7 GB (56.45% of 17 GB) at 320s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 54s Peak memory utilization: 9.9 GB (57.91% of 17 GB) at 41s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 1s Peak memory utilization: 9.9 GB (57.91% of 17 GB) at 450s