Process completed with exit code 1.

Process completed with exit code 1.

The run was canceled by @github-actions[bot].

The run was canceled by @github-actions[bot].

The run was canceled by @github-actions[bot].

The run was canceled by @github-actions[bot].

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. 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.

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

Failed to restore gradle-home-v1|macOS|react-native-build[110edf7f4bb3d9c29c78ec2341460f62]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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: gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: dev-packages/e2e-tests/react-native-versions/0.84.0/RnDiffApp/ios/*.log. No artifacts will be uploaded.

Failed to restore gradle-home-v1|Linux|react-native-build[c060efdbe1fb452784212c3848e4e935]-2f99cdb727c483fd8e80da6eb56961c26048f367: Error: Cache service responded with 400

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

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

'syscall' is deprecated: first deprecated in iOS 10.0 - syscall(2) is unsupported; please switch to a supported interface. For SYS_kdebug_trace use kdebug_signpost(). [-Wdeprecated-declarations]

Failed to restore gradle-home-v1|macOS|react-native-build[cabaacd85ee3acb79ec394ec7ca5cf3d]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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: gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: dev-packages/e2e-tests/react-native-versions/0.71.19/RnDiffApp/ios/*.log. No artifacts will be uploaded.

Failed to restore gradle-home-v1|Linux|react-native-build[6a579b23163b53c178ace9079e037109]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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: gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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.

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

Failed to restore gradle-home-v1|macOS|react-native-build[43125785ca69810949390f76c7388f35]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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: gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: dev-packages/e2e-tests/react-native-versions/0.71.19/RnDiffApp/ios/*.log. No artifacts will be uploaded.

Failed to restore gradle-home-v1|Linux|react-native-build[452eed38b732b9ace524003ca73f8448]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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. 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]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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: gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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.

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

Failed to restore gradle-home-v1|macOS|react-native-build[7922bbf007081ab6bc08b99fcb3de7f4]-2f99cdb727c483fd8e80da6eb56961c26048f367: Error: Cache service responded with 400

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

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

'syscall' is deprecated: first deprecated in iOS 10.0 - syscall(2) is unsupported; please switch to a supported interface. For SYS_kdebug_trace use kdebug_signpost(). [-Wdeprecated-declarations]

Failed to restore gradle-home-v1|macOS|react-native-build[9edbddc77ea8f10a64e634f36dd5c834]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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: gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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.

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

Failed to restore gradle-home-v1|macOS|react-native-build[208dd7c20ee6c33a384430ab48eba74a]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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: gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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.

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

using '@_implementationOnly' without enabling library evolution for 'Sentry' may lead to instability during execution

Failed to restore gradle-home-v1|macOS|react-native-build[ac95e0619d5678a74744889af3c7563c]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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. 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]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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: gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: dev-packages/e2e-tests/react-native-versions/0.84.0/RnDiffApp/ios/*.log. No artifacts will be uploaded.

Failed to restore gradle-home-v1|Linux|react-native-build[f622e51cfb54a80189e83d8cac3f5a4c]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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. 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]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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, gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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.

More than one (4) device matching requirements (os:[] os_version:[>=18.0] model:[iphone 17]) have been found.

Failed to restore gradle-home-v1|macOS|react-native-test[43125785ca69810949390f76c7388f35]-2f99cdb727c483fd8e80da6eb56961c26048f367: 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, gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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.

More than one (4) device matching requirements (os:[] os_version:[>=18.0] model:[iphone 17]) have been found.

Failed to restore gradle-home-v1|macOS|react-native-test[7922bbf007081ab6bc08b99fcb3de7f4]-2f99cdb727c483fd8e80da6eb56961c26048f367: Error: Cache service responded with 400

Peak CPU utilization: 4.00 cores (99.90% of 4.00) at 190s Peak memory utilization: 9.3 GB (54.32% of 17 GB) at 180s

Peak CPU utilization: 10.72 cores (67.03% of 16.00) at 330s Peak memory utilization: 11 GB (21.17% of 50 GB) at 340s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 370s Peak memory utilization: 9.9 GB (57.58% of 17 GB) at 130s

Peak CPU utilization: 9.01 cores (56.29% of 16.00) at 270s Peak memory utilization: 7.7 GB (15.34% of 50 GB) at 270s

Peak CPU utilization: 4.00 cores (99.95% of 4.00) at 190s Peak memory utilization: 9.5 GB (55.03% of 17 GB) at 35s

Peak CPU utilization: 9.41 cores (58.84% of 16.00) at 290s Peak memory utilization: 7.9 GB (15.72% of 50 GB) at 290s

Peak CPU utilization: 9.05 cores (56.55% of 16.00) at 270s Peak memory utilization: 10 GB (20.65% of 50 GB) at 580s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 1s Peak memory utilization: 9.5 GB (55.08% of 17 GB) at 270s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 330s Peak memory utilization: 9.9 GB (57.60% of 17 GB) at 120s

Peak CPU utilization: 4.00 cores (99.98% of 4.00) at 210s Peak memory utilization: 9.5 GB (55.23% of 17 GB) at 240s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 190s Peak memory utilization: 9.4 GB (54.87% of 17 GB) at 220s

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

Peak CPU utilization: 7.21 cores (45.09% of 16.00) at 270s Peak memory utilization: 9.9 GB (19.67% of 50 GB) at 300s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 200s Peak memory utilization: 9.5 GB (55.14% of 17 GB) at 320s

Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 120s Peak memory utilization: 11 GB (63.82% of 17 GB) at 210s