Repository navigation
[NativeAOT-iOS] MacCatalyst fails to start/log nativeaot.SmokeTests tests #105804
Copy link
Copy link
Closed
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-arm64area-Infrastructure-monoos-maccatalystMacCatalyst OSMacCatalyst OS
Milestone
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=804204
Build error leg or test failing:
nativeaot.SmokeTests.Reflection,nativeaot.SmokeTests.StackTraceMetadatanativeaot.SmokeTests.Preinitialization
Affected CI: maccatalyst-arm64 Release AllSubsets_NativeAOT_RuntimeTests (runtime-extra-platforms)
The test are failing either with:
XHarness exit code: 83 (APP_LAUNCH_FAILURE)
[05:10:37.6845280] The application cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-600 "procNotFound: no eligible process with specified descriptor" UserInfo={_LSLine=387, _LSFunction=_LSAnnotateAndSendAppleEventWithOptions}
or
XHarness exit code: 82 (RETURN_CODE_NOT_SET)
Failed to detect application's exit code. The log file was empty / not found at /tmp/helix/working/9D2308EA/w/9FFA08F1/uploads/Reports/nativeaot.SmokeTests.Reflection/Reflection/net.dot.nativeaot_SmokeTests_Reflection.log
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorPattern": "nativeaot/SmokeTests/.+\\[FAIL\\]",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=804204
Error message validated: [nativeaot/SmokeTests/.+\[FAIL\]]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/12/2024 10:07:58 AM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 5 | 9 | 26 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-arm64area-Infrastructure-monoos-maccatalystMacCatalyst OSMacCatalyst OS
Activity
matouskozak commentedon Aug 1, 2024
Could it be related to #102882 @ivanpovazan @kotlarmilos ?
[-][NativeAOT-iOS] MacCatalyst fails to start/log `nativeaot.SmokeTests.Reflection` tests[/-][+][NativeAOT-iOS] MacCatalyst fails to start/log `nativeaot.SmokeTests` tests[/+]ivanpovazan commentedon Aug 1, 2024
I don't think so, that issue did disable the test, but we had a failure with it on tvos-arm64 even before in:
#90460
If I remember correctly the behavior was similar to what you are getting ie the device log showed correct output in the logs but test return value was not what the test runner expected.
I would check if we are properly rooting every possible test infra assembly when we build these tests with NativeAOT.
ivanpovazan commentedon Aug 2, 2024
@matouskozak @kotlarmilos could you check this:
ivanpovazan commentedon Sep 12, 2024
@matouskozak just FYI: updated the
ErrorPatternand a newer build failing with the same reason.kotlarmilos commentedon Oct 10, 2025
nativeaot.SmokeTests.Preinitializationfails on MacCatalyst arm64 only. Here is the stack trace:Instead of throwing (and catching) a managed exception, the runtime reports a SIGSEGV.
@MichalStrehovsky Do you have any changes in mind that could have caused this? This seems to be an old issue, and it reproduces only on maccatalyst arm64.
kotlarmilos commentedon Oct 13, 2025
These tests appear to fail randomly. The issue is not related to any specific machine, and all are running the same OS version.
MichalStrehovsky commentedon Oct 29, 2025
The test is triggering and catching a
NullReferenceExceptionand that's a SIGSEGV. We're supposed to handle it and convert it to a managed exception. So either that is not happening or we hit another SIGSEGV while translating. Hard to say without a dump or without having it under debugger. I'm not aware of issue like this elsewhere. I don't think we touched hardware exception handling in a while.A lot of random failures get bucketed under this issue because the
ErrorPatternis too broad.kotlarmilos commentedon Jul 22, 2026
This is failing in servicing branches only, closing this issue