UWP Release mode builds fail sporadically in CI

[Arlodotexe]

The issue

When the CI compiles the Strix Music app in release mode, there's a high chance that release mode will fail and need to be rerun. The error message is:

Generating native code Launching 'C:\Users\VssAdministrator.nuget\packages\runtime.win10-arm.microsoft.net.native.compiler\2.2.7-rel-27913-00\tools\ARM\ilc\Tools64\nutc_driver.exe @"D:\a\1\s\src\Platforms\StrixMusic.UWP\obj\ARM\Release\ilc\intermediate\MDIL\StrixMusic.rsp"'

[error]C:\Users\VssAdministrator.nuget\packages\microsoft.net.native.compiler\2.2.7-rel-27913-00\tools\Microsoft.NetNative.targets(801,5): Error : Internal Compiler Error

C:\Users\VssAdministrator.nuget\packages\microsoft.net.native.compiler\2.2.7-rel-27913-00\tools\Microsoft.NetNative.targets(801,5): error : Internal Compiler Error [D:\a\1\s\src\Platforms\StrixMusic.UWP\StrixMusic.UWP.csproj]

[error]C:\Users\VssAdministrator.nuget\packages\microsoft.net.native.compiler\2.2.7-rel-27913-00\tools\Microsoft.NetNative.targets(801,5): Error : ILT0005: 'C:\Users\VssAdministrator.nuget\packages\runtime.win10-arm.microsoft.net.native.compiler\2.2.7-rel-27913-00\tools\ARM\ilc\Tools64\nutc_driver.exe @"D:\a\1\s\src\Platforms\StrixMusic.UWP\obj\ARM\Release\ilc\intermediate\MDIL\StrixMusic.rsp"' returned exit code 1

1>C:\Users\VssAdministrator.nuget\packages\microsoft.net.native.compiler\2.2.7-rel-27913-00\tools\Microsoft.NetNative.targets(801,5): error : ILT0005: 'C:\Users\VssAdministrator.nuget\packages\runtime.win10-arm.microsoft.net.native.compiler\2.2.7-rel-27913-00\tools\ARM\ilc\Tools64\nutc_driver.exe @"D:\a\1\s\src\Platforms\StrixMusic.UWP\obj\ARM\Release\ilc\intermediate\MDIL\StrixMusic.rsp"' returned exit code 1 [D:\a\1\s\src\Platforms\StrixMusic.UWP\StrixMusic.UWP.csproj]

Done Building Project "D:\a\1\s\src\Platforms\StrixMusic.UWP\StrixMusic.UWP.csproj" (default targets) -- FAILED.

The solution

Build locally in release mode and find/fix the cause of the build error. Use Visual Studio and set the build output level to at least "Detailed" to get the most useful information.

[Arlodotexe]

184 contains all of our attempts and findings so far.

201 might be able to help us sidestep the issue entirely by having build validation done on the contributor's machine(s).