Uh oh!
There was an error while loading. Please reload this page.
Fix ILLink testing to run with asserts enabled - #128349
Conversation
Tagging subscribers to this area: @agocke, @dotnet/illink |
Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/f632a37c-7d8a-4995-a242-7e54d135b5a2 Co-authored-by: jtschuster <36744439+jtschuster@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the runtime-linker-tests Azure Pipelines definition to run ILLink (and the trimming test runs that depend on ILLink) with Debug-built tools, while keeping the overall pipeline in Release configuration.
Changes:
- Pass
/p:ToolsConfiguration=Debugto the ILLink test job build and test invocations. - Pass
/p:ToolsConfiguration=Debugthrough to trimming test executions (viaextraTestArgs) so they also use Debug-built tools. - Update the first section header comment to reflect the Debug-tools intent.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
MichalStrehovsky
commented
May 21, 2026
This didn't trigger the relevant ILLink leg It only executed these: ![]() But it should have executed these: ![]() The ILLink_Runtime_Testing are the unit tests, this only executed the trimming test apps. I'm now seeing in main: This is some runtime/src/tools/illink/src/linker/Linker.Steps/MarkStep.cs Lines 2109 to 2112 in fdea14d |
…ns and typereasons to fix tests. (#128461) #128349 started running tests with a Debug illink, which is tripping an assert. I missed the fact that the illink unit tests didn't run and now those tests are failing: #128349 (comment) To fix, add this reason as an expected reason for marking a method or a type.


Set ToolsConfiguration=Debug to enable asserts in ILLink unit tests and the libraries tests that we run trimmed.