You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9b76f60
Browse filesBrowse the repository at this point in the historyBrowse files
* refactor(ios-runner): key runner retry rules on typed connect-failure reasons
The runner connect path now publishes `details.runnerConnectFailureReason`
(`xcodebuild_exited_early`, `runner_connect_refused`,
`runner_endpoint_probe_exhausted`) where it builds each failure, and the
retry table keys those three rules on that field instead of our own
message text. The remaining text rules read only foreign text (Node's
fetch/net/http errors, Xcode's device-busy text) under a renamed
`foreignMessageIncludesAll` field, each naming its tool.
Test doubles that stood in for these failures now carry the typed reason,
and each converted rule has a test that the reason, not the message,
decides the verdicts.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* refactor(ios-runner): drop the restart composition typed reasons made redundant
With the connect-failure reasons exclusive, no error that grants a restart
before send can also carry a terminal connect verdict, so the restart
predicate reads its own axis. Doc comments now say which failures carry a
BootFailureReason and that the rows above the startup block include
foreign-runtime text matchers.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* test(apple-runner): move connect-retry classification tests to their owning file
runner-client.test.ts asserted shouldRetryRunnerConnectError and
isRetryableRunnerError, both exported by runner-error-classification.ts and
already covered there, growing it past the test-file size ratchet. Move the
one uncovered case (runner_endpoint_probe_exhausted keeps the connect loop
retrying) into runner-error-classification.test.ts and drop the rest as
duplicate message-sniff coverage.
Give runnerConnectFailure a reason-keyed default message so the retry
suite's repeated connect-refused/probe-exhausted fixtures fit on one line
again, bringing runner-command-retry.test.ts back to its merge-base length.
---------
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
0 commit comments