.NET 9 Preview 7 often fails to build on arm64

[omajid]

Describe the Bug

I have been trying to build the .NET 9 Preview 7 release on a number of OS/architecture combinations. I have noticed that VMR builds often fail on arm64.

1. arm64 + CentOS Stream 10 fails with Analyzer 'Microsoft.Interop.Analyzers.CustomMarshallerAttributeAnalyzer' threw an exception of type 'System.InvalidProgramException' with message 'Common Language Runtime detected an invalid program.

   • Full log: https://download.copr.fedorainfracloud.org/results/@dotnet-sig/dotnet-preview/centos-stream-10-aarch64/07905791-dotnet9.0/builder-live.log.gz
   • Also reported as Analyzer 'Microsoft.Interop.Analyzers.CustomMarshallerAttributeAnalyzer' threw an exception of type 'System.InvalidProgramException runtime#106904

2. arm64 + RHEL 9 failed with CSC : error AD0001: Analyzer 'Microsoft.NetCore.CSharp.Analyzers.Runtime.CSharpDetectPreviewFeatureAnalyzer' threw an exception of type 'System.NullReferenceException' with message 'Object reference not set to an instance of an object.'

   • Full log: https://download.copr.fedorainfracloud.org/results/@dotnet-sig/dotnet-preview/rhel-9-aarch64/07905791-dotnet9.0/builder-live.log.gz

3. arm64 + Fedora ELN and arm64 + Fedora Rawhide failed with a crash: error MSB6006: "csc.dll" exited with code 139.

   • Full log: https://download.copr.fedorainfracloud.org/results/@dotnet-sig/dotnet-preview/fedora-eln-aarch64/07905791-dotnet9.0/builder-live.log.gz

This doesn't seem to affect every build or every arm64 platform. As an example, an attempt on arm64 + Fedora 39 worked, as did arm64 + RHEL 8.

Steps to Reproduce

On an arm64 machine, the following sequence of steps can fail:

git clone https://github.com/dotnet/dotnet
cd dotnet
git checkout v9.0.0-preview.7.24405.7
./prep-source-build.sh
./build.sh --source-only

Other Information

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[mthalman]

This is the tracking issue for that: dotnet/dnceng#3305. We had previously encountered it in our VMR builds: #4451. But it went away. Other builds are still seeing it apparently. It's not limited to the VMR.

[MichaelSimons]

@omajid - Can you clarify what SDK you are using to build? Are you using the version prep retrieves (e.g. 9.0.100-preview.7.24380.2)?

[omajid]

Are you using the version prep retrieves (e.g. 9.0.100-preview.7.24380.2)?

Yes. All the build logs show:

Welcome to .NET 9.0!
---------------------
SDK Version: 9.0.100-preview.7.24380.2

[omajid]

This is the tracking issue for that: dotnet/dnceng#3305.

Ah, I didn't see that. Shall I close this issue in source-build, then?

[MichaelSimons]

Ah, I didn't see that. Shall I close this issue in source-build, then?

My preference would be for you to add a comment to dotnet/dnceng#3305 and then close this one.

[omajid]

Okay, comment added there.