coveralls
commented
2 years ago Pull Request Test Coverage Report for Build 2767d7d27-PR-865
- 7 of 70 (10.0%) changed or added relevant lines in 3 files are covered.
- 2 unchanged lines in 1 file lost coverage.
- Overall coverage decreased (-0.2%) to 45.273%
| Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
|---|---|---|---|---|---|
| internal/log/log.go | 5 | 10 | 50.0% | ||
| cmd/tegola/cmd/root.go | 2 | 18 | 11.11% | ||
| internal/log/zap.go | 0 | 42 | 0.0% | ||
| <!-- | Total: | 7 | 70 | 10.0% | --> |
| Files with Coverage Reduction | New Missed Lines | % | ||
|---|---|---|---|---|
| internal/log/log.go | 2 | 64.75% | ||
| <!-- | Total: | 2 | --> |
| Totals | |
|---|---|
| Change from base Build 6387c6785: | -0.2% |
| Covered Lines: | 5593 |
| Relevant Lines: | 12354 |
gdey
Re-opening this as discussed.
As discussed in #831 I added the option to use structured logs with uber/zap while falling back to the currently implemented default if
--loggeris not specifically used. Log levels conform to the current implementation with the exception of log levelTRACEthat is not supported by zap. I use Debug as a fall back here.