Update Microsoft.BuildXL.Processes #9476
Merged
Conversation
This file contains 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
ladipro
approved these changes
Nov 30, 2023
mpysson
approved these changes
Nov 30, 2023
rainersigwald
approved these changes
Nov 30, 2023
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.
Update Microsoft.BuildXL.Processes
The primary motivation behind this update is to bring in a bug fix related to the BuildXL.Process assembly depending on BuildXL.Tracing, which is not available in the package.
Before and after:
This change also adjusts a breaking change to
ChildProcessesToBreakawayFromSandbox, as well as added some extra logic associated with the reason behind the breaking change which supportsdotnetscenarios better. This is just future-proofing though since reporting file accesses via detours is currently only available in MSBuild.exe.