Assertion Failure: Test crashed with signal ill.

signal ill probably means that the program crashed with a SIGILL signal, which is the standard way for Intel code to trap (that is, deliberately crash). See Understanding the exception types in a crash report.

To debug this you need to get a crash report from your CI system. Can you do that?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

hi @maveric94, were you able to resolve this? having the same issue for my iOS UI test

@appledev99928 Well, these crashes do not occur too often, so for now I just added collection of crashlogs from ~/Library/Logs/DiagnosticReports/. So when they do happen, I could at least examine crashreport

@DTS Engineer Dear Apple, kindly bump this issue. Xcode Cloud Test action always fail with the same error - " App Name (7274) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed with signal ill before starting test execution.)) "

I'm also seeing this consistently within Xcode Cloud, but haven't seen it locally. I've downloaded the crash log bundle, and it contains one for AccessibilityControlsExtension and a bunch for MercuryPosterExtension (examples attached). I don't really know what either of those things are, but can't find any references to my code in either.

I was able to work around this issue by setting the Host Application to "None" for my test scheme. This stops Xcode Cloud from attempting to start up the application binary.