ci(e2e): give the iOS build room to finish a cold build - #106
Merged
Conversation
The push-to-main run for #105 came back `cancelled` with no error in the log. It was not concurrency — cancel-in-progress is scoped to pull_request — and not a lost runner. `Build iOS (required)` simply ran out its `timeout-minutes: 45`, and Actions reports a timed-out job as cancelled. The margin was never there to begin with. The last green run on main took 44m50s for the same job: ten seconds of slack. A cold .app cache makes the job pay for a full Xcode release build (31m) plus the simulator boot, so whether main goes green came down to how fast a given macOS runner felt that morning. The cancel also skipped every cache-save post step, so the next run starts cold again and re-rolls the same dice. Raise both iOS build jobs to 75 minutes. A warm fingerprint hit still finishes in minutes; this only buys the cold path enough room to land. Claude-Session: https://claude.ai/code/session_01Fe92vvdc4R3F4BDBFoLcw1
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.
The push-to-main run for #105 came back
cancelledwith no error in the log. Worth ruling out the usual suspects first: it was not concurrency (cancel-in-progressis scoped topull_request, so a push-to-main run is never killed by a newer one) and not a lost runner.Build iOS (required)ran out itstimeout-minutes: 45. Actions reports a timed-out job ascancelled, which is why the run looks like someone hit the button.The margin was never there. Timings from the two runs:
Ten seconds. A cold
.appcache makes the job pay for a full Xcode release build — 31 minutes in the failed run — plus the simulator boot, so whether main went green came down to how fast a given macOS runner felt that morning.It also compounds: the cancel skipped every cache-save post step, so the next run starts cold too and re-rolls the same dice.
Both iOS build jobs go to 75 minutes. A warm fingerprint hit still finishes in minutes — this only buys the cold path enough room to land.
Claude-Session: https://claude.ai/code/session_01Fe92vvdc4R3F4BDBFoLcw1