Repository navigation
fix: reduce phased report log verbosity - #270
Open
JakkulaVeerababu wants to merge 1 commit into
Open
JakkulaVeerababu wants to merge 1 commit into
JakkulaVeerababu wants to merge 1 commit into
Conversation
Author
|
@adobe/open-source-office I completed and email-verified the Adobe CLA today, but the Adobe CLA check still reports "No signed agreements were found" after closing and reopening this PR as instructed. Could you please refresh or verify the agreement for this contributor? The same issue affects PR #271. |
4 of 10 tasks
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.
Description
Move the merged-report reduction message from INFO to DEBUG so normal runs do not emit the full scenario result collection. The message remains available when debug logging is enabled.
Related Issue
Closes #100
Motivation and Context
The report-reduction log includes the complete result list and is diagnostic rather than user-facing output. Logging it at INFO creates unnecessary noise in normal test runs.
How Has This Been Tested?
mvn -s C:/Users/LENOVO/AppData/Local/Temp/omnirush/maven-settings.xml -pl phased-testing-testng -am testgit diff --checkNote: the repository's
.mvn/settings.xmlhas a leading blank line before its XML declaration, so Maven was run with a temporary empty settings file to bypass that pre-existing environment/configuration issue.