runtime: Common job failure: msbuild MSB4166 error

This seems to be a common, non-repeatable, job failure reason for the Linux arm64 jobs (maybe others as well?)

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

This seems to mostly occur during the Docker build of the tests.

E.g., https://ci.dot.net/job/dotnet_coreclr/job/master/job/arm64_cross_checked_ubuntu16.04_innerloop/43/consoleFull

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 1
Comments: 24 (17 by maintainers)

Commits related to this issue

Configure MSBuild debug path and save any logs We have had many problems in the CI with MSBuild failing, and not capturing the failure logs. See https://github.com/dotnet/coreclr/issues/20236. So, ... — committed to BruceForstall/coreclr by BruceForstall 5 years ago

Most upvoted comments

We’ve encountered this while multiple pipelines are trying to build different projects stored in a single solution (single repo) – hope it helps.

sercanparan on Aug 6, 2019

The issue is now hitting Azure DevOps CI build and test jobs.

For example, in https://dnceng.visualstudio.com/public/_build/results?buildId=70179 Test pri0 Linux_musl x64 checked Job has failed with:

2019-01-10T19:18:33.2451899Z MSBUILD : error MSB4166: Child node "2" exited prematurely. Shutting down. Diagnostic information may be found in files in "/tmp/" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.
2019-01-10T19:18:33.2764510Z 
2019-01-10T19:18:33.2768447Z Build FAILED.
2019-01-10T19:18:33.2768538Z 
2019-01-10T19:18:33.2768768Z MSBUILD : error MSB4166: Child node "2" exited prematurely. Shutting down. Diagnostic information may be found in files in "/tmp/" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.
2019-01-10T19:18:33.2777524Z     0 Warning(s)
2019-01-10T19:18:33.2778197Z     1 Error(s)
2019-01-10T19:18:33.2778269Z 
2019-01-10T19:18:33.2778475Z Time Elapsed 00:04:05.08
2019-01-10T19:18:33.3742116Z Command execution failed with exit code 1.
2019-01-10T19:18:33.3775644Z ERROR: An error occured in /__w/1/s/Tools/dotnetcli/dotnet /__w/1/s/Tools/run.exe /__w/1/s/config.json build -Project=/__w/1/s/tests/build.proj -MsBuildLog=/flp:Verbosity=normal;LogFile=/__w/1/s/bin/Logs/Tests_Managed.Linux.x64.Checked.log;Append=true -MsBuildWrn=/flp1:WarningsOnly;LogFile=/__w/1/s/bin/Logs/Tests_Managed.Linux.x64.Checked.wrn;Append=true -MsBuildErr=/flp2:ErrorsOnly;LogFile=/__w/1/s/bin/Logs/Tests_Managed.Linux.x64.Checked.err;Append=true -MsBuildEventLogging=/l:BinClashLogger,Tools/Microsoft.DotNet.Build.Tasks.dll;LogFile=binclash.log -BuildArch=x64 -BuildType=Checked -BuildOS=Linux. Check logs under /__w/1/s.
2019-01-10T19:18:33.3778658Z Failed to build Managed tests build (build tests). See the build logs:
2019-01-10T19:18:33.3778923Z     /__w/1/s/bin/Logs/Tests_Managed.Linux.x64.Checked.log
2019-01-10T19:18:33.3779281Z     /__w/1/s/bin/Logs/Tests_Managed.Linux.x64.Checked.wrn
2019-01-10T19:18:33.3780309Z     /__w/1/s/bin/Logs/Tests_Managed.Linux.x64.Checked.err
2019-01-10T19:18:33.3905727Z ##[error]Bash exited with code '1'.

@RussKeldorph This would very costly failure as soon as we switch to Azure DevOps CI since now if only one job fails in order to properly validate PR you would need to restart all the jobs (default or custom triggered) and hope that MSBuild won’t fail again.

echesakov on Jan 10, 2019