WIP: chore(ci): tune harness timeouts and add diagnostics for iOS flakiness#158
Open
WIP: chore(ci): tune harness timeouts and add diagnostics for iOS flakiness#158
Conversation
- bridgeTimeout 300s→90s so failed attempts don't eat the entire step timeout - bundleStartTimeout 15s→45s (default was too tight, app connects in ~13s on success) - maxAppRestarts 2→3 for more internal retries - forwardClientLogs: true for visibility into app-side logs - terminate simulator app in nuke_harness between retries - dump_diagnostics before/after each attempt (sim state, app running, ports, memory) - step timeout 15m→25m to allow all 5 external retries - expanded failure debug step (crash reports, network logs, error-level logs)
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
1 participant
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.
Investigating ~30-40% iOS harness failure rate. The root cause: the harness's
bundleStartTimeout(default 15s) is too tight for CI — the app connects in ~13s on success, missing the window on slower runners. Combined withbridgeTimeout: 300s, a single failed Jest run eats the entire 15min step timeout, making the 5-attempt retry loop useless.Changes:
bridgeTimeout300s→90s,bundleStartTimeout15s→45s,maxAppRestarts2→3xcrun simctl terminate)dump_diagnosticsbefore/after each attempt (sim state, app status, ports, memory)forwardClientLogs: truefor app-side console output