.Net 10 RC2 seems to ignore NODEREUSE under Linux

[mbenedykconfigit]

Describe the bug

On a 3 out of 5 builds in linux CI env, build is failing with:
error MSB4166: Child node "5" exited prematurely. Shutting down. Diagnostic information may be found in files in "/tmp/msbuild-debug" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.

No MSBuild_*.failure.txt is being created.

This issue started to occur when I started using Net 10 RC2, no problems with Net 9.

/property:UseSharedCompilation=false /nodeReuse:fals /maxcpucount:1 arguments doesn't help as well,
MSBUILDDISABLENODEREUSE=1 doesn't work either

To Reproduce

Hard to define reproductions steps when everythink works so far and right after Net 10 RC2 update it started failing....

dotnet build XXX.sln --configuration LinuxRelease --framework net10.0 /property:UseSharedCompilation=false /nodeReuse:false /maxcpucount:1

Exceptions (if any)

error MSB4166: Child node "5" exited prematurely. Shutting down. Diagnostic information may be found in files in "/tmp/msbuild-debug" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.

Further technical details

details of dotnet --info

.NET SDK: Version: 10.0.100-rc.2.25502.107 Commit: 89c8f6a112 Workload version: 10.0.100-manifests.8798a653 MSBuild version: 18.0.0-preview-25502-107+89c8f6a11

Runtime Environment:
OS Name: ubuntu
OS Version: 24.04
OS Platform: Linux
RID: linux-x64
Base Path: /usr/share/dotnet/sdk/10.0.100-rc.2.25502.107/

.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.

Host:
Version: 10.0.0-rc.2.25502.107
Architecture: x64
Commit: 89c8f6a112

.NET SDKs installed:
8.0.120 [/usr/share/dotnet/sdk]
8.0.206 [/usr/share/dotnet/sdk]
8.0.317 [/usr/share/dotnet/sdk]
8.0.414 [/usr/share/dotnet/sdk]
8.0.415 [/usr/share/dotnet/sdk]
9.0.110 [/usr/share/dotnet/sdk]
9.0.205 [/usr/share/dotnet/sdk]
9.0.305 [/usr/share/dotnet/sdk]
10.0.100-rc.2.25502.107 [/usr/share/dotnet/sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.20 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.21 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.9 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 10.0.0-rc.2.25502.107 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.20 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.21 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.9 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 10.0.0-rc.2.25502.107 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
None

Environment variables:
DOTNET_MULTILEVEL_LOOKUP [0]
DOTNET_NOLOGO [1]
DOTNET_ROOT [/usr/share/dotnet]
DOTNET_SKIP_FIRST_TIME_EXPERIENCE [1]
DOTNET_VERSION [10.0.x]
DOTNET_VERSION_RAVEN [8.0.x]

- The IDE (VS / VS Code/ VS4Mac) you're running on, and its version: GithubActions

[mbenedykconfigit]

it seems it is related with our CI setup

[mbenedykconfigit]

I'm reopening this issues.
In Linux environment Net 10 RC2 ignores nodes cfg, it is clearly visible in detailed verbosity when multiple nodes are being used

[baronfel]

Disabling Node Reuse doesn't stop the system from making multiple nodes to do its work on, it just prevents those created nodes from sticking around after the build completes. I would expect the /maxcpucount you're setting to make it so that only one node (the primary node) is working though...

Can you try running a build with

• MSBUILDDEBUGCOMM set to 1 so that we can see node communication logs
• MSBUILDDEBUGPATH set to your CWD to ensure there are no permissions issues writing the logs
• -bl to create a binlog
  and then zip those outputs up and upload them?

We have seen some issues at the .NET Runtime level with spawning nodes on macOS that we think are related to some issues with the entitlements, but testing with GA candidate builds has shown those issues being solved, so it may just be a point-in-time thing with RC2.

[dkogithub]

Here’s an update on this issue, originally created by my colleague 🙂
The problem mentioned in the title has been resolved by using the /maxcpucount:1 parameter. This option wasn’t initially included in the Nuke build, but after some adjustments, it’s now properly taken into account — allowing us to run it on a single node.

However, the issue with the child node failure still persists, which was not the case with Net9 SDK. Unfortunately, I couldn’t find any meaningful information about the exception or the error itself, either in the communication logs or the binlog.

I can share the communication trace logs here, but due to security restrictions, I’m unable to share the binlog.

msbuild-failure-diagnostics-node-fail.zip

So, I think we can close this ticket due to original issue is gone now.

Thanks for help.