Closed Letme closed 5 years ago
Merging #17 into master will increase coverage by
0.34%
. The diff coverage is4.44%
.
@@ Coverage Diff @@
## master #17 +/- ##
==========================================
+ Coverage 17.04% 17.39% +0.34%
==========================================
Files 1 1
Lines 176 184 +8
==========================================
+ Hits 30 32 +2
- Misses 146 152 +6
Impacted Files | Coverage Δ | |
---|---|---|
mlx/coverity.py | 17.39% <4.44%> (+0.34%) |
:arrow_up: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 32d8c20...3a9d573. Read the comment docs.
We were logging in and retrieving stream and project information from coverity server with each node. This is not needed and is now done when builder initializes. It also enabled us to print nicer warning outputs when there was a login error, but we still do not fail build with it. It is up for external tools (mlx.warnings) to error in case warnings are unwanted. It also means that in case you have plugin in
conf.py
, but you don't use it (no directives), it will not print errors or fail your builds.When bad login credentials are provided:
When stream is wrong:
I only moved
initialize_environment
andprocess_coverity_nodes
into common classSphinxCoverityConnector
which makes sure that coverty_service and project_name variables are shared. Because of that I also was able to move error handling (initialized in init), which now prints login failed information at node position in document (so in case there are no nodes and plugin fails, we also do not get any warnings).Fixes #12
Fixes #16