chore: Tighten Harness CI timeouts#3983
Draft
mrousavy wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What changed
Cherry-picks the Harness timeout config from #3981 onto
main.bridgeTimeout: 120s -> 45sbundleStartTimeout: 90s -> 30s in CIplatformReadyTimeout: explicit 60s instead of Harness default 300smaxAppRestarts: 4 -> 1 in CI, local stays at 2This only uses official Harness config APIs. No shell-level timeout/watchdog logic.
Why
#3981 was accidentally merged into
chore/harness-crash-reporting-draft, notmain. Currentmainstill has the old 120s bridge timeout and 90s bundle timeout, so the in-progressmainHarness run is not testing the shorter timeout config.The log-based validation from recent Harness runs still applies: when controller actually runs, the work is seconds-long; the costly failures are dead Harness waits where
runTests(controllerFile)never returns. LoweringbridgeTimeoutshould reduce that waste without cutting into observed successful test-file execution.Validation
git diff --check HEAD~1..HEADCI=true bun -e "import config from './apps/simple-camera/rn-harness.config.mjs'; if (config.bridgeTimeout !== 45000 || config.bundleStartTimeout !== 30000 || config.platformReadyTimeout !== 60000 || config.maxAppRestarts !== 1 || config.detectNativeCrashes !== true) throw new Error(JSON.stringify(config)); console.log('Harness CI timeout config ok')"