Assertion Failure: Test crashed with signal ill.

Question

maveric94 OP

Created Feb ’23

Replies 3

Boosts 0

Views 2.7k

Participants 3

I get this error from time to time in UI tests when they are run on CI. Any ideas what might be causing this error?

Screenshot 2023-02-28 at 00.59.28.png

Answered by DTS Engineer in 746243022

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"

Boost

Answer 1

DTS Engineer OP

Apple

Feb ’23

Accepted Answer

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"

2

Answer 2

appledev99928 OP

Mar ’23

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

0

Answer 3

maveric94 OP

Mar ’23

@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

1