build.sh command on the runtime repo backed to mainline is hanging

[Vishwanatha-HD]

Description

I am seeing a hang issues while executing a "build.sh" command manually on runtime repo backed to mainline branch on s390x machines.. The below command hangs indefinitely and when I do a "ctrl+c", I get back the prompt..

./build.sh /p:UsingToolMicrosoftNetCompilers=false /p:NoPgoOptimize=true --portablebuild false /p:DotNetBuildFromSource=true /p:DotNetBuildSourceOnly=true /p:DotNetBuildTests=true --cmakeargs -DCLR_CMAKE_USE_SYSTEM_BROTLI=true --cmakeargs -DCLR_CMAKE_USE_SYSTEM_ZLIB=true --runtimeconfiguration Release --librariesConfiguration Debug /p:PrimaryRuntimeFlavor=Mono --warnAsError false --subset clr+mono+libs+host+packs+libs.tests
Determining projects to restore...
Restored /home/redhat/.nuget/packages/microsoft.dotnet.arcade.sdk/10.0.0-beta.25058.4/tools/Tools.proj (in 2.09 sec).
Determining projects to restore...
I also tried backing the runtime repo to "v10.0.0-preview.1.25080.5" tag.. Even then it hangs..

I manually untarred the dotnet sdks on s390x machine and did a "dotnet new console --name "Hello" --no-restore".. This is working fine and it confirms that the SDKs that are built for s390x are functional..

I haven't validated this issue on other archs..

Reproduction Steps

The below command should work and start building the runtime repo..
./build.sh /p:UsingToolMicrosoftNetCompilers=false /p:NoPgoOptimize=true --portablebuild false /p:DotNetBuildFromSource=true /p:DotNetBuildSourceOnly=true /p:DotNetBuildTests=true --cmakeargs -DCLR_CMAKE_USE_SYSTEM_BROTLI=true --cmakeargs -DCLR_CMAKE_USE_SYSTEM_ZLIB=true --runtimeconfiguration Release --librariesConfiguration Debug /p:PrimaryRuntimeFlavor=Mono --warnAsError false --subset clr+mono+libs+host+packs+libs.tests

Expected behavior

The command should not hang indefinitely and it should start building the runtime repo.

Actual behavior

The build.sh command hangs indefinitely

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

[Vishwanatha-HD]

cc: @omajid @tmds @uweigand @saitama951 @giritrivedi @medhatiwari

[giritrivedi]

Hello @Vishwanatha-HD
I will take a look to see if it gets reproduced on my machine.

[uweigand]

Hi @Vishwanatha-HD is this once again the mono_loader_lock deadlock described here? #93686

The symptom there was also a hang during the restore phase. But it would be good to verify by creating backtraces of the hanging processes and checking whether they hand in mono_loader_lock ..

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

[Vishwanatha-HD]

Sure @uweigand.. I will try to get more info on the reason why it's hanging and update you here.. Thanks..

[giritrivedi]

@Vishwanatha-HD The issue is not reproducible on local machines. Tried both on RHEL and Ubuntu distros with mainline branch.
Please let us know if it hangs again on your machine .