-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Bug]: MSBuild crashes with "MSB0001: Internal MSBuild Error: must be valid" #10342
Comments
Strong suspect: #10102 |
This came up in dotnet#10342. This doesn't fix it but makes the error less awful.
This came up in dotnet#10342. This doesn't fix it but makes the error less awful.
@JanKrivanek I got a couple hits, all of them with this log:
|
Thank you @akoeplinger for being on top of this without me giving you proper info about inserted versions! This helps! Stay tunned - this is near the top of my priority list :-) |
Got another hit with a different type (TaskLoggingContext):
|
@akoeplinger - would you be able to point me to the builds as well? Binlog(s) would be super helpful |
They're mostly from https://dev.azure.com/dnceng-public/public/_build/results?buildId=742084&view=results and https://dev.azure.com/dnceng-public/public/_build/results?buildId=742554&view=results, but it's a bit hard to find the relevant failures. I'll dig up the other ones tomorrow but here's one from this build and the corresponding binlog (renamed as zip so GitHub accepted it): source-inner-build.zip
|
Issue Description
Copied from dotnet/dnceng#3304
I queried Kusto and it seems we started seeing this more often after we bumped the VMR build to use a bleeding-edge preview 7 SDK. I see one hit in the last 60 days but since we bumped to P7 SDK about 10 hours ago we already hit this three times.
Steps to Reproduce
Build the VMR repo. The failure only happens occasionally.
Expected Behavior
No crash.
Actual Behavior
There is a crash.
Analysis
No response
Versions & Configurations
No response
The text was updated successfully, but these errors were encountered: