roslyn: Intermittent error "csc.dll exited with code 255"

Version Used: The version embedded in the Dotnet Sdk version 2.2.0-preview1-007796.

Steps to Reproduce:

  1. Run ./build.cmd in aspnet/Universe. Build may or may not fail. Seemingly even with the same commits.

Expected Behavior: Successful compilation.

Actual Behavior: Recieve error: C:\BuildAgent\work\33bdfc1cae7b2a38\.dotnet\x64\sdk\2.2.0-preview1-007522\Roslyn\Microsoft.CSharp.Core.targets(84,5): error MSB6006: "csc.dll" exited with code 255.

Tracked here on the ASP.NET end. Complete logs can be found here but unfortunately the above error seems to be the only relevant part. If there’s anything we can do to gather more data from this let us know, we can deploy that then update the issue with the new information.

About this issue

  • Original URL
  • State: open
  • Created 7 years ago
  • Reactions: 1
  • Comments: 38 (29 by maintainers)

Commits related to this issue

Most upvoted comments

@savalik

The best way to proceed is to grab a crash dump of the compiler and / or provide a binlog (it sometimes contains the stack trace of the crash). We should use a new issue to track that though as this is tracking a specific multi-core JIT bug.

and Microsoft.Net.Compilers)

Please note that this package is deprecated. In general we do not support customers depending on this or Microsoft.Net.Compilers.Toolset, in their solutions. These packages are meant for internal binary distribution and hot patching customer bugs, not for long term use. Instead we ask that customers use the .NET SDK installs with the compiler version they desire.

Why nobody work on it? How people build and analyze code with ci/cd? Are there some workarounds?