Conversation
dougbu
left a comment
There was a problem hiding this comment.
We can't use this SDK until it no longer worsens the file contention issues in our build. Suspect it works in dotnet/runtime only because they use the Microsoft.Build.Traversal SDK.
| <!-- Properties for Package Validation --> | ||
| <!-- We only want to check for API changes in servicing branches --> | ||
| <PropertyGroup Condition=" '$(IsServicingBuild)' != 'true' "> | ||
| <DisablePackageBaselineValidation>true</DisablePackageBaselineValidation> |
There was a problem hiding this comment.
Don't we need to set properties somewhere to inform Microsoft.DotNet.PackageValidation of the baseline package version once we are in servicing❔
There was a problem hiding this comment.
correct we dont need this, baseline validation wont run by default
i am planning to make it a part of sdk before preview 7 change. so maybe waiting here is the best option |
|
@Anipik we're concerned about this going in to the dotnet SDK if it winds up causing these build races for us - it might block us from updating to a newer SDK. @rainersigwald we're seeing more instances of the file contention issue here, but on different projects:
How can we help investigate? |
|
I doubt it'll help but let's see if @TanayParikh's targeted fix (#34137) does the trick. Might need something similar for other file contention issues this PR brings to the forefront. |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
See Build channel in Teams for discussion of prior build contention investigations. Starting point is a binary log for whatever job looks worst to you. |
|
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Fixes #33981
Still a couple outstanding questions -