Repository navigation
ci: purge the agent-device apple-runner artifact before iOS retry attempts - #96
Merged
Merged
Conversation
…empts (#76) The restored runner artifact can fail hard (dyld: libcurl.4.dylib) because the cache key omits the macOS host build. Remove ~/.agent-device/apple-runner before attempt 2 of iOS device-contract jobs so retries rebuild the runner from scratch; first attempts keep the cached fast path and contract failures still never retry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…le-runner-before-retry
Owner
Author
|
No changeset needed |
1 similar comment
Owner
Author
|
No changeset needed |
…le-runner-before-retry
Owner
Author
|
No changeset needed |
Skipping the install step on a Pods cache hit let the React Native CLI reinstall pods mid-build with the runner image's unpinned system CocoaPods, which fails when that executable is older than the one that generated Podfile.lock. The pinned install is nearly a no-op on a warm cache and reconciles a stale cached Pods directory. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
Author
|
No changeset needed |
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.
Closes #76 (CI overhaul 9/9, plan #59, map #53).
What
In
scripts/run-device-contract-job.mjs, iOS device-contract jobs now delete~/.agent-device/apple-runner(with a log line) at the top of the retry iteration — which is only reachable after an exit-75/signal infrastructure failure — so attempt 2 rebuilds the runner from scratch instead of restoring the same broken artifact.Per #56 research (flake 3), the restored runner artifact can fail with
dyld: Library not loaded: libcurl.4.dylibbecause the cache key omits the macOS host build, and the rebuild fallback only fires on retriable health failures — so the dyld failure is a hard error today. The upstream cache-key report is filed separately.Acceptance criteria
~/.agent-device/apple-runnerdirectory, visible in the attempt log via thePurging …line.index > 1).Tests
New script-execution test in
src/__tests__/issue39-device-contract.test.tsruns the real job script against stub child scripts in a temp workspace with an overriddenHOME, asserting: iOS retry purges and logs; first attempt keeps the cache; contract failure (exit 1) never retries or purges; Android retries leave the artifact untouched. Full suite, typecheck and lint pass.🤖 Generated with Claude Code