resque / resque / 875 / 3

46%

1-x-stable: 46%

Pull #1439

travis-ci

<a href="https://github.com/resque/resque/commit/<a class=hub.com/resque/resque/commit/164176f19a5bb29c65d3491b0f209f41634e4010">164176f19<a href="https://github.com/resque/resque/commit/164176f19a5bb29c65d3491b0f209f41634e4010">&quot;&gt;worker: do not trigger verbose logging if env variables are not set

When setting a custom logger the logger state is lost due to a
regression added in the following commit:

,----
| commit </a><a class="double-link" href="https://github.com/resque/resque/commit/<a class="double-link" href="https://github.com/resque/resque/commit/87ae6d5e1cd6ebc498dc0a04ada74dc770c7facf">87ae6d5e1</a>">87ae6d5e1</a><a href="https://github.com/resque/resque/commit/164176f19a5bb29c65d3491b0f209f41634e4010">
| Author: Jacob Green &lt;jacob@nationbuilder.com&gt;
| Date:   Mon Jan 25 11:22:17 2016 -0500
|
|     Refactor worker#initialize
`----

The verbose and very_verbose setter methods are always called, even when
no verbose environment variables are set. This makes a custom logger
loose its level or custom formatter.

Signed-off-by: Lucas Dutra Nunes <ldnunes@ossystems.com.br>

398 of 1159 relevant lines covered (34.34%)

0.35 hits per line