Repository navigation
build-ios-app: a launch that starts nothing is made again - #1057
Merged
Merged
Conversation
iOS Build & Simulator Test fails on and off, master included (86de120, 62ce2a6) and branches that touch nothing iOS (5 of the last 30 runs). Every failure has the same shape: "simctl launch --console-pty" writes nothing for the whole 60 s cap, not the app's first line and not the "bundle: pid" simctl prints when it has started an app, and the verify step reports "expected test PASS output not found". A passing launch has the app's first line at once and the test's PASS within 5 to 9 s. So --verify now stops a launch that has written nothing in 20 s, terminates the app and launches again, up to three times; a launch that has started is given the whole 60 s, as before, and an app that starts and does not pass fails at once, not retried. On a failure the number of launches, the booted devices, the app's container and any crash report are printed, so the next one says more than "not found". Checked against a stand-in xcrun: a passing app passes in one launch; one launch that hangs silently then a passing one passes in two; three silent hangs fail after three; an app that starts and fails fails after one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0195u6z6W3TbdAx7jg6RqhYy
10 of 11 tasks
pdfinn
pushed a commit
that referenced
this pull request
Nov 3, 2026
Brings in #1057: the iOS verify step relaunches a simulator launch that started nothing, the one failure left on this branch (iOS Build & Simulator Test). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0195u6z6W3TbdAx7jg6RqhYy
pdfinn
pushed a commit
that referenced
this pull request
Nov 3, 2026
Brings in #1057: the iOS verify step relaunches a simulator launch that started nothing, the one failure left on this branch (iOS Build & Simulator Test). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0195u6z6W3TbdAx7jg6RqhYy
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
iOS Build & Simulator Test fails on and off, in 5 of the last 30 CI runs. That includes master (86de120 and 62ce2a6) and branches that change nothing on iOS: #1054 twice, plus an earlier
claude/kind-euler-f3ufm5head. Every failure looks the same:xcrun simctl launch --console-ptywrites nothing for the whole 60 s cap. The app's first line never appears, and neither does theos.infernode.ios: <pid>line simctl prints once it has started an app. simctl never started the app.VERIFY FAILED: expected test PASS output not found.A passing launch writes
InferNode: emu_run(...)at once and the test'sPASSwithin 5–9 s (five passing runs measured today). So the 60 s cap is not too tight. This is a launch that never happens.Changes
build-ios-app.sh --verify:The root cause in CoreSimulator is not established; this handles the failure mode as observed, and the added output is there to catch the cause.
Testing
bash -n build-ios-app.sh.The verify step was run on Linux against a stand-in
xcrunthat reproduces the observed hang (writes nothing, never returns), with the waits scaled down:xcrunNot run on macOS. This PR's own iOS job is the first real run.
Checklist
.disbuild artifacts committed fromappl/ortests/Generated by Claude Code