Skip to content
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

Please add some --quiet option or similar #652

Closed
Vampire opened this issue Aug 27, 2019 · 3 comments
Closed

Please add some --quiet option or similar #652

Vampire opened this issue Aug 27, 2019 · 3 comments

Comments

@Vampire
Copy link
Contributor

Vampire commented Aug 27, 2019

Pitest is way too verbose by default for inclusion in a Gradle run for example.
It would be nice if it had some option to be quiet except for warnings and errors,
so that the Gradle plugin or a Gradle build script can set it up so that info logging is only shown if info level logging is enabled, and verbose if debug logging is enabled. (The latter is already possible with verbose = logger.isDebugEnabled).

Gradle builds for example should by default be very quiet except for warnings and errors, so that those are better seen and only show informational messages if info-level logging is enabled.

@zielint0
Copy link

zielint0 commented Apr 18, 2020

@hcoles
Is there any chance to implement it?

@binkley
Copy link

binkley commented Jul 13, 2020

I have a similar experience with the Maven plugin:

  1. Researching the code base, the Log class hard-codes the INFO level
  2. I didn't find uses of the setLevel method except within this class, ie, no configuration call to it
  3. Experimented with -DPIT.level=WARNING both for Maven's JVM, and the <jvmArg> configuration for the plugin: No effect

FYI -- I used "PIT.level" after rereading the JDK's LogManager docs, and checking the source of Log for the logger name.

@hcoles
Copy link
Owner

hcoles commented Mar 2, 2022

#934 added a verbosity parameter which allows the amount of noise to be configured.

@hcoles hcoles closed this as completed Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants