RunVSTest: Avoid parsing UT console output looking for errors or warnings#630
Merged
RunVSTest: Avoid parsing UT console output looking for errors or warnings#630
Conversation
johnterickson
approved these changes
Jun 20, 2025
dfederm
force-pushed
the
fix-runvstest-logging
branch
from
53d3e31 to
ce44d02
Compare
johnterickson
approved these changes
Jun 20, 2025
rainersigwald
approved these changes
Jun 20, 2025
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
3 participants
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.
Today if a unit test logs a message which to MSBuild looks like an error, the task will unexpectedly fail.
This changes the logging call from
Log.LogMessageFromTextto simplyLog.LogMessageto avoid this behavior.