-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
dotnet build
returns exit code 1
even when the build passes
#74328
Comments
This probably needs a binlog |
Here's the binlog referenced in the log |
Tagging subscribers to this area: @dotnet/area-meta Issue DetailsThis happens randomly. One example:
|
Added ErrorMessage signature to get this issue auto-detected by Build analysis |
It looks like this is specifically happening during If you look at the binlogs, the arguments passed, I don't know what might cause this, it could be an SDK or MSBuild issue. |
Here's the tree of msbuild commits this scenario is working with: https://github.com/dotnet/msbuild/commits/5d102ae37 |
Is there a minimal repro someone can provide for this? |
I am hitting it every time on main, HEAD: cc9d465, running: WasmBuildTests InvariantGlobalizationTests for Browser, wasm.
So we're looking for After fixing this one, we are getting new errors.
When we check EDIT: |
Tagging subscribers to 'arch-wasm': @lewing Issue Details
This happens randomly. One example:
ReportSummary
|
this is specific to WASM, right? |
@ilonatommy The |
@ilonatommy Also, yours is a different issue. This one is about |
Seen in this release/7.0-rc2 PR: #75675 Note that the actual failure message is #75429 but it was closed as dupe of this one. Queue: Installer Build and Test coreclr Linux_musl_x64 Release Error:
|
I really need local repro. Does anyone knows how to? |
I don't have a local repro, but I see lots of 7.0 rolling runs failing Microsoft.DotNet.CoreSetup.Test.* Frequency of Microsoft.DotNet.CoreSetup.Test.* failures -- moved to top post. |
see also #76091 |
I guess there are multiple failure modes.
|
Seen in a release/7.0 unrelated PR: #76073
|
The binlogs are in a non-obvious place for the Installer tests. They get uploaded as a build artifact - for example, for the failure you linked, you can find the binlog in the Installer-Logs-coreclr--OSX_x64-Release artifact of the build under a subdirectory matching the test project that was being built or published (in that example, |
Seen in this 7.0 servicing PR: #76874 |
Fixed by updating to .NET 7 GA that has msbuild server disabled. |
This has resulted in a number of failures in the Installer and wasm tests.
Frequency of failures:
Installer-coreclr-Linux_musl_x64-Release
17x - Microsoft.DotNet.CoreSetup.Test
Installer-coreclr-OSX_x64-Release
23x failures - AppHost.Bundle.Tests
Related Runfo queries:
Original Report
This happens randomly. One example:
Build, and log:
Report
Summary
The text was updated successfully, but these errors were encountered: