Skip to content

use verbosity flags to drive diagnostics logging level #3809

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 27, 2021

Conversation

tomerd
Copy link
Contributor

@tomerd tomerd commented Oct 19, 2021

motivation: allow users to specify verbosity which would impact how much diagnostic information is outputed

changes:

  • add "very-verbose" CLI flag
  • drive diagnostics logging level based on verbosity flags: verbose == .info, very-verbose == .debug
  • filter diagnostic printing based on log level
  • pass logLevel where appropriate instead of isVerbose
  • add test

@tomerd
Copy link
Contributor Author

tomerd commented Oct 19, 2021

@swift-ci please smoke test

@tomerd tomerd added the ready Author believes the PR is ready to be merged & any feedback has been addressed label Oct 19, 2021
@tomerd tomerd self-assigned this Oct 20, 2021
motivation: allow users to specify verbosity which would impact how much diagnostic information is outputed

changes:
* add "very-verbose" CLI flag
* drive diagnostics logging level based on verbosity flags: verbose == .info, very-verbose == .debug
* filter diagnostic printing based on log level
* pass logLevel where appropriate instead of isVerbose
* add test
@tomerd tomerd force-pushed the diagnostics-verbosity branch from b2c31a7 to 7b02188 Compare October 26, 2021 22:44
@tomerd
Copy link
Contributor Author

tomerd commented Oct 26, 2021

@swift-ci please smoke test

@tomerd tomerd merged commit 4f86d6b into swiftlang:main Oct 27, 2021
@tomerd
Copy link
Contributor Author

tomerd commented Oct 27, 2021

@neonichu @abertelrud @elsh @yim-lee with this change in, we can now make use of emitting "info" and "debug" information more liberally since it will be filtered out in the output unless run in verbose or very-verbose modes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready Author believes the PR is ready to be merged & any feedback has been addressed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants