Repository navigation
ci(ios): retry a shard once after host trouble - #29
Merged
Merged
Conversation
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 standard macOS runner overloads, so the iOS E2E shards fail in about 2 of 3 full runs, each time on a different case. A shard now runs once more in the same job when the classifier marks every attempt-1 failure as host trouble, and a readiness or relaunch timeout under high load now counts as host trouble. The release gate re-derives that verdict from the attempt-1 evidence (
validateShardEvidenceine2e/helpers/ios-shards.mjs).Breaking: the iOS shard job deadline goes from 45 to 70 minutes so that two attempts fit.
Review focus:
retryReasonine2e/helpers/host-health.mjs, the only path to a second attempt.🤖 Generated with Claude Code