Skip to content

ci(e2e): boot the runner's iPhone 17 Pro and give the iOS job 90 minutes - #3

Closed
kacperkapusciak wants to merge 1 commit into
mainfrom
ci/ios-simulator-boot
Closed

kacperkapusciak wants to merge 1 commit into
mainfrom
ci/ios-simulator-boot

Conversation

@kacperkapusciak

@kacperkapusciak kacperkapusciak commented Nov 11, 2026 •

Copy link
Copy Markdown
Member

The iOS job on #1 timed out at 60 minutes during Run e2e. Where the time went:

Step Time
expo run:ios --configuration Release 35 min
simctl create + bootstatus -b 7 min 23 s, then ended with status -1
e2e booting the simulator again 3.5 min
Tests until the timeout 13 min
  • The job now boots the iPhone 17 Pro the runner image ships on the pinned iOS-26-5 runtime, instead of creating a new simulator whose first boot is slow. Same approach as mobile.yml in e2e-inc/e2e. If the image drops that runtime, the step fails and prints the available ones, so the pin can't silently change.
  • timeout-minutes for ios goes from 60 to 90. The Release build alone uses more than half of the old limit.
  • Doesn't touch what ci(e2e): fix the Android job on main #2 changes (artifact upload, Android build, tests/settings.e2e.ts).

Follow-up: caching the iOS build per native fingerprint (@expo/fingerprint + @expo/repack-app, as e2e-inc/e2e does) would remove most of the 35 minutes.

Verified

Ran it locally: no - CI-only change. The simulator lookup (simctl list devices available -j | jq ...) returns the iOS 26.5 iPhone 17 Pro on a Mac with Xcode 27.2.

View guided diff Turn on auto-fix

A simulator made with simctl create spent over 7 minutes on its first boot and the e2e engine booted it again, so with the 35-minute Release build the job hit its 60-minute limit.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

View guided diff | Turn on auto-fix | Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant