fix(android): Use safeExtGet for compileSdkVersion in expo-handler #6318
e2e-v2.yml
on: pull_request
auth_token_check
/
auth_token_check
2s
Ready-to-merge gate
/
Missing "ready-to-merge" label
4s
diff_check
/
diff_check
14s
detect-changes
/
Detect file changes
7s
Matrix: react-native-build
Matrix: metrics
Matrix: react-native-test
Annotations
11 errors, 23 warnings, and 13 notices
|
Build RN 0.85.1 new hermes android production no
The run was canceled by @github-actions[bot].
|
|
Build RN 0.85.1 new hermes android production no
The operation was canceled.
|
|
Build RN 0.71.19 legacy hermes android production no
The run was canceled by @github-actions[bot].
|
|
Build RN 0.71.19 legacy hermes android production no
The operation was canceled.
|
|
metrics (legacy, android)
The run was canceled by @github-actions[bot].
|
|
metrics (legacy, android)
The operation was canceled.
|
|
Build RN 0.85.1 legacy hermes android production no
The run was canceled by @github-actions[bot].
|
|
Build RN 0.85.1 legacy hermes android production no
The operation was canceled.
|
|
metrics (new, android)
The run was canceled by @github-actions[bot].
|
|
metrics (new, android)
The operation was canceled.
|
|
End-to-End Tests V2
The run was canceled by @github-actions[bot].
|
|
Resource Utilization
Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.
|
|
Resource Utilization
Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.
|
|
Resource Utilization
Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.
|
|
Resource Utilization
Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.
|
|
Resource Utilization
Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.
|
|
Build RN 0.85.1 new hermes android production no
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/
|
|
Build RN 0.85.1 new hermes android production no
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
Build RN 0.85.1 new hermes android production no
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.
|
|
Build RN 0.85.1 new hermes android production no
Failed to restore gradle-home-v1|Linux|react-native-build[2e394487bbb10b9b425940f5677b5782]-a1612d2982e8a6b8dc08ff0b7cf052d85ad2ab28: Error: Cache service responded with 400
|
|
Build RN 0.71.19 legacy hermes android production no
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/
|
|
Build RN 0.71.19 legacy hermes android production no
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
Build RN 0.71.19 legacy hermes android production no
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.
|
|
Build RN 0.71.19 legacy hermes android production no
Failed to restore gradle-home-v1|Linux|react-native-build[452eed38b732b9ace524003ca73f8448]-a1612d2982e8a6b8dc08ff0b7cf052d85ad2ab28: Error: Cache service responded with 400
|
|
metrics (legacy, android)
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/
|
|
metrics (legacy, android)
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
metrics (legacy, android)
Failed to restore gradle-home-v1|Linux|metrics[0afb79acc8a8328fb6bd71072249636c]-a1612d2982e8a6b8dc08ff0b7cf052d85ad2ab28: Error: Cache service responded with 400
|
|
Build RN 0.85.1 legacy hermes android production no
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/
|
|
Build RN 0.85.1 legacy hermes android production no
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
Build RN 0.85.1 legacy hermes android production no
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.
|
|
Build RN 0.85.1 legacy hermes android production no
Failed to restore gradle-home-v1|Linux|react-native-build[b784d8fb7b56d42925371c0c125bc27f]-a1612d2982e8a6b8dc08ff0b7cf052d85ad2ab28: Error: Cache service responded with 400
|
|
metrics (new, android)
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/
|
|
metrics (new, android)
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
metrics (new, android)
Failed to restore gradle-home-v1|Linux|metrics[419c195f369f6f7487088abdf4d1d9d2]-a1612d2982e8a6b8dc08ff0b7cf052d85ad2ab28: Error: Cache service responded with 400
|
|
Resource Utilization
Peak CPU utilization: 1.47 cores (36.79% of 4.00) at 10s
Peak memory utilization: 7.5 GB (43.80% of 17 GB) at 8s
|
|
Resource Utilization
Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 3s
Peak memory utilization: 8.1 GB (47.32% of 17 GB) at 9s
|
|
Resource Utilization
Peak CPU utilization: 1.64 cores (41.00% of 4.00) at 14s
Peak memory utilization: 7.1 GB (41.42% of 17 GB) at 8s
|
|
Resource Utilization
Peak CPU utilization: 0.84 cores (20.97% of 4.00) at 8s
Peak memory utilization: 7.3 GB (42.58% of 17 GB) at 8s
|
|
Resource Utilization
Peak CPU utilization: 2.90 cores (72.52% of 4.00) at 4s
Peak memory utilization: 7.9 GB (46.18% of 17 GB) at 9s
|
|
Resource Utilization
Peak CPU utilization: 2.97 cores (74.25% of 4.00) at 17s
Peak memory utilization: 8.8 GB (51.42% of 17 GB) at 17s
|
|
Resource Utilization
Peak CPU utilization: 0.54 cores (13.45% of 4.00) at 10s
Peak memory utilization: 7.9 GB (46.01% of 17 GB) at 11s
|
|
Resource Utilization
Peak CPU utilization: 0.72 cores (17.98% of 4.00) at 18s
Peak memory utilization: 8.5 GB (49.26% of 17 GB) at 18s
|
|
Resource Utilization
Peak CPU utilization: 4.03 cores (25.19% of 16.00) at 160s
Peak memory utilization: 5.3 GB (10.44% of 50 GB) at 210s
|
|
Resource Utilization
Peak CPU utilization: 4.00 cores (24.97% of 16.00) at 170s
Peak memory utilization: 4.0 GB (7.95% of 50 GB) at 170s
|
|
Resource Utilization
Peak CPU utilization: 3.48 cores (21.77% of 16.00) at 220s
Peak memory utilization: 5.9 GB (11.66% of 50 GB) at 220s
|
|
Resource Utilization
Peak CPU utilization: 3.89 cores (24.34% of 16.00) at 180s
Peak memory utilization: 6.0 GB (11.81% of 50 GB) at 220s
|
|
Resource Utilization
Peak CPU utilization: 3.74 cores (23.38% of 16.00) at 250s
Peak memory utilization: 5.3 GB (10.47% of 50 GB) at 250s
|