TEMPORARY: Overlay custom MSBuild for dotnet/msbuild#12927 investigation#66003
Draft
ilonatommy wants to merge 31 commits intodotnet:mainfrom
Draft
TEMPORARY: Overlay custom MSBuild for dotnet/msbuild#12927 investigation#66003ilonatommy wants to merge 31 commits intodotnet:mainfrom
ilonatommy wants to merge 31 commits intodotnet:mainfrom
Conversation
Add custom Microsoft.Build.Tasks.Core.dll from the MSBuild team with additional logging to diagnose intermittent MSB3030 'Could not copy file' errors in parallel builds. The DLL is overlaid onto the SDK's copy in eng/build.sh and eng/build.ps1 after SDK initialization, with SHA256 verification output in the build log. DO NOT MERGE - investigation branch only. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Windows PowerShell 5.1 (used on CI agents) only supports 2 arguments to Join-Path. Nest the calls instead. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The env var may not be set in all CI build configurations. Fall back to RepoRoot/.dotnet which configure-toolset.ps1 always forces. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Scheduled task script that: - Checks Build Analysis check run to see if CI is done - Searches AzDO logs for MSB3030/MSB3026 errors - If not found, merges upstream/main and retriggers CI - If found, logs alert and stops Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Mar 28, 2026
Open
Open
Open
…ild-bootstrap-investigation
Member
Author
|
/azp run aspnetcore-ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Member
Author
|
/azp run aspnetcore-ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Member
Author
🚨 MSB3030 "File Not Found" Error Detected (Automated)Build: #1365043 Errors found:
Action required: Collect binlog from this build and share with MSBuild team (@OvesN on dotnet/msbuild#12927). This comment was posted automatically by the CI monitor script. |
This was referenced Apr 3, 2026
This was referenced Apr 6, 2026
New DLL: 18.4.0+a18aac5435e (build 20901) Old DLL: 18.4.0+6e61e96acff (build 17701) SHA256: 95684FA027FCA4A5212925F1E429D9C34C458715D1591872F28BE57C74E88810 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…estigation # Conflicts: # eng/Version.Details.props # eng/Version.Details.xml # global.json # src/Components/WebAssembly/WebAssembly/src/Properties/ILLink.Substitutions.xml # src/Components/test/E2ETest/Tests/WebAssemblyTrimmingTest.cs # src/Components/test/testassets/BasicTestApp/Index.razor # src/Components/test/testassets/Components.TestServer/Components.TestServer.csproj
Preview.3 removed FrameworkFileUtilities.RemoveRelativeSegments which the custom Tasks DLL depends on. Preview.1 has it. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
System.IO.FileHandleType was added in preview.3. With preview.1 pinned, this is not needed, but the merge brought in code that uses unqualified FileHandleType. Fully qualify to Microsoft.AspNetCore.Connections. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Revert SDK pin to preview.3 since V3 DLL is now compatible. SHA256: 5F3AE9B75488BBCBAB51A9954414BA5BC70A1D487B5EC789876697F8A1092E99 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The custom Tasks DLL calls RemoveRelativeSegments which was removed from the SDK's Framework DLL in preview.3. Overlay the matching Framework DLL from the same MSBuild build (18.4.0+a18aac54) to ensure compatibility. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE - Investigation branch only
Purpose
Overlay custom
Microsoft.Build.Tasks.Core.dllfrom the MSBuild team to diagnose intermittentMSB3030: Could not copy fileerrors during parallel CI builds.Tracking issue: dotnet/msbuild#12927
Known Build Error: #62807
hits from the known build issue happened on:
So it hits both Linux and Windows build legs, specifically during the large parallel compilation steps (Run build.sh, Run build.cmd, Build Installers). These are the jobs where /m parallelism triggers the race condition. Our overlay covers both build.sh and build.ps1, so we're
covered on all the failing legs.
❯ are these legs running on our playground PR?
What this does
Microsoft.Build.Tasks.Core.dll(with extra logging) toeng/msbuild-bootstrapeng/build.shandeng/build.ps1, overlays the custom DLL onto.dotnet/sdk<version>/Microsoft.Build.Tasks.Core.dllSHA256hashes to the build log so we can verify the overlay workedExpected outcome
=== MSBuild Bootstrap Overlay ===section confirming the DLL was replacedMSB3030 erroroccurs, the binlog will contain additional diagnostic information from the custom MSBuildHow to revert
Close this PR. No repo-wide changes are needed.
This PR should be updated automatically when my devbox's task scheduler detects that CI finished without error that we're waiting for.