docs: record confirmed CoreSimulator runner blocker
Android validation / emulator (35) (push) Failing after 4s
Android validation / emulator (37.0) (push) Failing after 9s
iOS validation / simulator (push) Failing after 1m5s
Android validation / build (push) Successful in 5m16s

Follow-up Mac job 1066 passed Node/checkout/Xcode/Swift lookup, then correctly failed the bounded simctl device-list probe after sixty seconds. Record the exact administrator-owned blocker without claiming Apple app validation.
This commit is contained in:
Yuvomi Mobile Contributors committed 2026-10-21 09:38:59 +02:00
1 parent 92dbd0e06d
commit 129eac675c
4 files changed
+18 -6

No files matched your search

+7 -1
View File
@@ -71,7 +71,13 @@ Evidence paths in the local external build directory:
preflight did not return during a 20-minute observation. No SwiftUI compile or
simulator/XCTest/Keychain/device success is claimed. Bounded, named tool probes
now fail with actionable diagnostics instead of silently hanging for the job's
full hour; their actual next Mac result still needs inspection.
full hour.
- Follow-up iOS run #8 (global 663), job 1066 at `92dbd0e`: Node, checkout,
`xcodebuild -version` and `xcrun --find swift` passed. The exact blocker is
**`xcrun simctl list devices available`**, which exceeded its 60-second deadline.
Preflight correctly failed; application builds/tests/archive were skipped, not
passed. The runner administrator must repair CoreSimulator availability for the
runner user before Apple application validation can proceed.
No Apple SDK application build, simulator UI test or physical-device result is
claimed from the Linux runs or the stalled Mac job. Runner prerequisites were