allow --log-level option in info#2714
Merged
bradgrantham-lunarg merged 1 commit intoLunarG:devfrom Mar 5, 2026
Merged
Conversation
MarkY-LunarG
approved these changes
Feb 23, 2026
948fb9f to
3443e1b
Compare
* Include tool_settings.h and take advantage of that
* Add log-level as an option
* This allows output to stdout but blocking warning output from
consumers like state setup or the frame marker warning
3443e1b to
76f90bf
Compare
zongdu-arm
pushed a commit
to zongdu-arm/gfxreconstruct
that referenced
this pull request
Mar 6, 2026
* Include tool_settings.h and take advantage of that
* Add log-level as an option
* This allows output to stdout but blocking warning output from
consumers like state setup or the frame marker warning
Bypass rules because info/ hasn't changed since last successful test run
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.
Before this change, the output of "gfxrecon-info --verbose" could not be reliably parsed as JSON because the output may have had logging warning or info messages interspersed in it. This is a change in line with #1917