Suppress MSB3026 warnings#65671
Merged
Merged
Conversation
github-actions
Bot
added
the
needs-area-label
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repo-wide build configuration to prevent transient MSBuild copy-retry warnings (MSB3026) from failing CI when /warnaserror is enabled (as it is in CI builds).
Changes:
- Demote
MSB3026from warning/error to message level viaMSBuildWarningsAsMessagesso retry-attempt noise does not fail builds. - Document the rationale inline in
Directory.Build.props.
BrennanConroy
approved these changes
Mar 6, 2026
Member
Author
|
/backport to release/10.0 |
Contributor
|
Started backporting to |
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.
MSBuild logs a copy failure as
MSB3026, and then retries. We often see this surface as:The build then retries the copy, and it usually succeeds, but CI still reports red due to
MSB3026. We can NoWarn it, since a subsequent copy failure in the retry gets logged as a different warning (MSB3021), so the build will still correctly fail in those cases.