Repository navigation
tvos-arm64 Mono AOT precompilation fails with Invalid IL code for multiple test assemblies #126458
Description
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1362636
Build error leg or test failing: System.Net.NameResolution.Functional.Tests.WorkItemExecution, System.Reflection.Context.Tests.WorkItemExecution, System.Text.Encoding.Extensions.Tests.WorkItemExecution
Pull request: #125441
Affected CI jobs: build_tvos_arm64_Release_AllSubsets_Mono
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "Precompiling failed",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Summary
On tvos-arm64 Mono Release (AOT mode), the Mono AOT compiler fails to precompile test assemblies with "Invalid IL code" errors:
Precompiling failed for aot-instances.dll with exit code 134
Unable to compile method ... due to: 'Invalid IL code in ...: IL_0000: ret'
3 work items affected:
- System.Net.NameResolution.Functional.Tests
- System.Reflection.Context.Tests
- System.Text.Encoding.Extensions.Tests
Note
This issue was filed with the assistance of GitHub Copilot.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1362636
Error message validated: [Precompiling failed]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/2/2026 10:17:08 AM UTC
Report
| Build | Repository | Test | Pull Request |
|---|---|---|---|
| 1681026 | dotnet/runtime | System.IO.FileSystem.DisabledFileLocking.Tests.WorkItemExecution |
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 1 | 1 | 1 |
Activity
dotnet-policy-service commentedon Apr 2, 2026
Tagging subscribers to 'os-tvos': @vitek-karas, @kotlarmilos, @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.
BrzVlad commentedon May 21, 2026
@kotlarmilos Any idea about this ? I seem to remember you fixed something similar at some point, with the issue being that we were passing the wrong processed assemblies to the compiler, some issue on the infrastructure side.
Looking at some logs seems like this might match on unrelated issues. Ex:
kotlarmilos commentedon May 22, 2026
This happens on Helix retries. I think the ILLinker runs on the first attempt, and if the job fails, it tries trimming again on the same payload, which has already been trimmed. Although the error message is too generic