3
100%
master: 100%

Ran 24 Sep 2019 12:51AM UTC

Files 19

Run time 1s

Badge

Embed ▾

Committed 24 Sep 2019 12:50AM UTC coverage: 100.0%. Remained the same

Job # TOX_ENV=cov-travis

Build Type

push

travis-ci

Committed by

rohanpm

Commit Message

logging: refactor --debug to be more useful

Currently, --debug is all or nothing.  If you pass it, you get
DEBUG logs from *every* logger - but that can be incredibly
verbose and may also mean the logs should be considered insecure
(with e.g. passwords potentially being logged, since we don't know
what might be logged from 3rd-party libraries).
That's effectively unusable in a production environment.

Let's make it more useful by categorizing the loggers and enabling
DEBUG logs for different sets of loggers depending on how many
times --debug was provided.  The idea is that we have:

- tier1 logger: the logger from this project itself
- tier2 loggers: closely related projects under our control
  (e.g. anything else in pubtools.* family)
- tier3 loggers: anything else

This way, `--debug' and `--debug --debug' might actually be useful
in production sometimes. `--debug --debug --debug` is for local
development only.

Run Details

572 of 572 relevant lines covered (100.0%)

1.0 hits per line

release-engineering / pubtools-pulp / 55 / 3
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 55.3 (TOX_ENV=cov-travis)

release-engineering / pubtools-pulp / 55 / 3 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 55.3 (TOX_ENV=cov-travis)

release-engineering / pubtools-pulp / 55 / 3
100%
master: 100%

README BADGES
x