Increase test verbosity - #6828
Conversation
Change `config["verbose"]` from `1` to `2` so that DEBUG-level logging from plugin import tasks and event hooks are emitted. (See `beets.plugins._set_log_level_and_params`.) `config["verbose"] == 2` does not appear to affect logging anywhere else in the codebase, while `config["verbose"] == 3` would enable output of messages logged via `BeetsLogger.extra_debug()`. Signed-off-by: Ross Williams <ross@ross-williams.net>
|
Thank you for the PR! The changelog has not been updated, so here is a friendly reminder to check if you need to add an entry. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #6828 +/- ##
=======================================
Coverage 74.97% 74.97%
=======================================
Files 163 163
Lines 21043 21043
Branches 3312 3312
=======================================
Hits 15777 15777
Misses 4514 4514
Partials 752 752 🚀 New features to boost your workflow:
|
|
|
I was wondering that myself, if maximum debug logging is the right way to go for tests, and I figured you would have a better sense of that. IMO, if |
|
Thinking about the future, this is actually a good idea - verbosity=2 is what we'd like to have indeed! |
Im working towards removing this extra debug level at some point 🤣 Feel free to have a look at #6553 and #6773 |
Description
Change
config["verbose"]from1to2so that DEBUG-level logging from plugin import tasks and event hooks are emitted. (Seebeets.plugins._set_log_level_and_params.)config["verbose"] == 2does not appear to affect logging anywhere else in the codebase, whileconfig["verbose"] == 3would enable output of messages logged viaBeetsLogger.extra_debug().To Do
DocumentationChangelog