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 5345d94
Browse filesBrowse the repository at this point in the historyBrowse files
ci(1874): declare the diagnose lane and stop it misreading its own loop
Two defects in the harness #1874 depends on, both found while dispatching it
after #2035 merged.
It classified every non-`passed` iteration as a stall. #2035 gave the looped
test an XCTSkipIf on an ambient software keyboard, so an environment flip would
now be reported as a 100% stall rate; a selection matching nothing reported the
same. It reads xcodebuild's own verdict word instead, counting passed/skipped/
failed/no-result separately.
It captured cadence only for failing iterations. Since #2035 the commit wait
absorbs an episode that keeps making progress, so an episode passes — the loop
was reporting only the episodes bad enough to still be red. It now also captures
any iteration slower than SLOW_PASS_MS.
That threshold is measured, not guessed: the 2026-08-26 dispatch ran 50 healthy
iterations at 628-1131 ms across two arm64 legs, against a 2487 ms/5-poll
episode on record and two single-poll outliers of 4.0 s and 14.1 s in that same
dispatch. Keyed on elapsed time rather than poll count because those outliers
settled on the FIRST poll: the time went somewhere before the wait, which is
precisely the evidence the dumps were not collecting.
Also adds the #1781 lane declaration the file never had — Catches, Evidence,
Cost, and a Kill criterion that names the commit which should delete it. No gate
manifest entry: the `gate: swift-runner-ios` input here is the shared build
action's, and ios.yml owns that gate.
0 commit comments