Skip to content

fix(core): Lazy-load Metro internal modules to prevent Expo 55 import errors #14023

fix(core): Lazy-load Metro internal modules to prevent Expo 55 import errors

fix(core): Lazy-load Metro internal modules to prevent Expo 55 import errors #14023

Triggered via pull request April 7, 2026 10:06
Status Cancelled
Total duration 3m 51s
Artifacts

native-tests.yml

on: pull_request
Ready-to-merge gate  /  Missing "ready-to-merge" label
2s
Ready-to-merge gate / Missing "ready-to-merge" label
diff_check  /  diff_check
9s
diff_check / diff_check
detect-changes  /  Detect file changes
4s
detect-changes / Detect file changes
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 3 warnings, and 2 notices
android
Process completed with exit code 1.
Native Tests
The run was canceled by @github-actions[bot].
ios
The run was canceled by @github-actions[bot].
ios
The operation was canceled.
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/
android
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
android
Failed to restore gradle-home-v1|Linux|test-android[654d28888e6d02b21725c0f3f2b06371]-435cafa8aa5ed50c2b9a78e450c465d8cd154d50: Error: Cache service responded with 400
Resource Utilization
Peak CPU utilization: 15.39 cores (96.18% of 16.00) at 42s Peak memory utilization: 2.0 GB (3.98% of 50 GB) at 49s
Resource Utilization
Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 54s Peak memory utilization: 9.6 GB (55.83% of 17 GB) at 160s