Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
In the failed
v1release run, simulator boot completed, butsimctl appinfostayed pending until the seven-minute startup deadline. Harness only reported a generic platform readiness timeout, which hid the command that stalled.This extends our Harness 1.5.0 Bun patches to include the active simulator command, simulator name, and time spent in that command in the timeout error. Finite setup subprocesses receive session cancellation and are terminated when initialization times out. Completed commands are cleared so a later failure does not point to an earlier successful operation.
I verified 27 startup checks with CI's pinned Bun version, including stalls during discovery, boot, app lookup, plist parsing, installation, and configuration. The runtime checks cover the real session's error propagation and cleanup, preservation of command errors, and termination of a child process that ignores SIGTERM. Release and staging tests also pass.
Upstream tracking: callstackincubator/react-native-harness#300