Skip to content

MSB6006: "csc.dll" exited with code 143 #89820

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vpapidokha opened this issue Jul 23, 2021 · 6 comments
Closed

MSB6006: "csc.dll" exited with code 143 #89820

vpapidokha opened this issue Jul 23, 2021 · 6 comments
Labels
area-VM-coreclr needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration
Milestone

Comments

@vpapidokha
Copy link

Summary of the issue:
Randomly getting the error during CI process, but don't see any kind of regularity. As much as we don't see detailed information about problem neither in the log output nor on the internet.

Log from build process:

13:55:33 /usr/share/dotnet/sdk/5.0.100/Roslyn/Microsoft.CSharp.Core.targets(71,5): error MSB6006: "csc.dll" exited with code 143. [/var/lib/jenkins/workspace/*.csproj]
13:55:33 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.
13:55:33 /usr/share/dotnet/sdk/5.0.100/Roslyn/Microsoft.CSharp.Core.targets(71,5): warning MSB5021: Terminating the task executable "dotnet" and its child processes because the build was canceled. [/var/lib/jenkins/workspace/*.csproj]
13:55:33 /usr/share/dotnet/sdk/5.0.100/Roslyn/Microsoft.CSharp.Core.targets(71,5): error MSB4181: The "Csc" task returned false but did not log an error. [/var/lib/jenkins/workspace/*.csproj]

The mentioned in the log output file MSBuild_*.failure.txt is absent. We have several in our /tmp directory, but the time of their creation is significantly differentiate. However, I see a bunch of files that have relevant time stamps, but didn't find any helpful info about them.

srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:54 MSBuild90636
srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:55 MSBuild90655
srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:55 MSBuild90671
srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:55 MSBuild90689
srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:55 MSBuild90707
srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:57 MSBuild92987
srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:57 MSBuild93003
srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:57 MSBuild93019
srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:57 MSBuild93038
srwxrwxr-x   1 jenkins       jenkins           0 Jul 23 13:57 MSBuild93066

Version used:
dotnet --version 5.0.100

OS:
Linux version 3.10.0-1127.10.1.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC) ) dotnet/sdk#1 SMP

Steps to reproduce:

dotnet build -c Releas project_name.sln

Expected Behavior:
Build SUCCESS.

Actual Behavior:
Build FAILED.

@ghost
Copy link

ghost commented Jul 23, 2021

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.

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jul 23, 2021
@joeloff joeloff transferred this issue from dotnet/sdk Aug 1, 2023
@ghost ghost added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Aug 1, 2023
@joeloff joeloff removed their assignment Aug 1, 2023
@joeloff
Copy link
Member

joeloff commented Aug 1, 2023

Had a chat with Jared. Suggested this was/is likely runtime related since there's no stack trace

@vcsjones vcsjones removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Aug 3, 2023
@mangod9
Copy link
Member

mangod9 commented Aug 3, 2023

Since this issue is two years old. @vpapidokha, does this continue to repro for you?

@mangod9 mangod9 removed the untriaged New issue has not been triaged by the area owner label Aug 3, 2023
@mangod9 mangod9 added this to the Future milestone Aug 3, 2023
@mangod9 mangod9 added the needs-author-action An issue or pull request that requires more info or actions from the author. label Aug 3, 2023
@ghost
Copy link

ghost commented Aug 3, 2023

This issue has been marked needs-author-action and may be missing some important information.

@vpapidokha
Copy link
Author

No,it stopped reproducing at some moment. But thanks for the response😅

@ghost ghost added needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration and removed needs-author-action An issue or pull request that requires more info or actions from the author. labels Aug 3, 2023
@mangod9
Copy link
Member

mangod9 commented Aug 3, 2023

Ok thanks for confirming, will close for now.

@mangod9 mangod9 closed this as completed Aug 3, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Sep 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-VM-coreclr needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration
Projects
None yet
Development

No branches or pull requests

5 participants