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.

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.

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

No files were found with the provided path: dev-packages/e2e-tests/react-native-versions/0.85.1/RnDiffApp/ios/*.log. No artifacts will be uploaded.

No files were found with the provided path: dev-packages/e2e-tests/react-native-versions/0.85.1/RnDiffApp/ios/*.log. No artifacts will be uploaded.

No files were found with the provided path: dev-packages/e2e-tests/react-native-versions/0.71.19/RnDiffApp/ios/*.log. No artifacts will be uploaded.

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. Actions will be forced to run with Node.js 24 by default starting June 16th, 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: actions/setup-java@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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: dniHze/maestro-test-action@bda8a93211c86d0a05b7a4597c5ad134566fbde4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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: dniHze/maestro-test-action@bda8a93211c86d0a05b7a4597c5ad134566fbde4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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: 1.68 cores (42.05% of 4.00) at 9s Peak memory utilization: 7.1 GB (41.08% of 17 GB) at 7s

Peak CPU utilization: 1.63 cores (40.77% of 4.00) at 7s Peak memory utilization: 7.9 GB (46.00% of 17 GB) at 10s

Peak CPU utilization: 0.73 cores (18.21% of 4.00) at 10s Peak memory utilization: 7.0 GB (40.48% of 17 GB) at 7s

Peak CPU utilization: 1.75 cores (43.65% of 4.00) at 2s Peak memory utilization: 7.3 GB (42.33% of 17 GB) at 7s

Peak CPU utilization: 0.75 cores (18.85% of 4.00) at 7s Peak memory utilization: 7.2 GB (42.02% of 17 GB) at 7s

Peak CPU utilization: 1.11 cores (27.75% of 4.00) at 8s Peak memory utilization: 8.9 GB (51.90% of 17 GB) at 12s

Peak CPU utilization: 1.43 cores (35.82% of 4.00) at 4s Peak memory utilization: 7.0 GB (40.88% of 17 GB) at 9s

Peak CPU utilization: 0.70 cores (17.52% of 4.00) at 7s Peak memory utilization: 7.8 GB (45.67% of 17 GB) at 12s

Peak CPU utilization: 8.96 cores (56.01% of 16.00) at 260s Peak memory utilization: 8.9 GB (17.72% of 50 GB) at 260s

Peak CPU utilization: 13.03 cores (81.41% of 16.00) at 310s Peak memory utilization: 10 GB (20.26% of 50 GB) at 290s

Peak CPU utilization: 7.05 cores (44.04% of 16.00) at 420s Peak memory utilization: 7.1 GB (14.08% of 50 GB) at 420s

Peak CPU utilization: 2.00 cores (49.89% of 4.00) at 11s Peak memory utilization: 8.4 GB (49.16% of 17 GB) at 9s

Peak CPU utilization: 2.14 cores (53.41% of 4.00) at 10s Peak memory utilization: 8.3 GB (48.58% of 17 GB) at 9s

Peak CPU utilization: 7.47 cores (46.66% of 16.00) at 280s Peak memory utilization: 8.3 GB (16.44% of 50 GB) at 580s

Peak CPU utilization: 9.32 cores (58.25% of 16.00) at 330s Peak memory utilization: 8.3 GB (16.49% of 50 GB) at 620s

Peak CPU utilization: 3.06 cores (19.11% of 16.00) at 270s Peak memory utilization: 8.8 GB (17.37% of 50 GB) at 360s