Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The verbosity for coverage reports doesn't work because of undefined constants:
Log.COVERAGE_VERBOSE
. A constantCOVERAGE_VERBOSE
is exported inserver/context/log.js
, but it's not implemented as a property ofLog
. SinceLog
is a named export, this constant doesn't work like the others fromConf
, and that's why that constant isundefined
there.Conf.IS_COVERAGE_VERBOSE
is used when generating a JSON summary report and when getting options through HTTP.Motivation and Context
Get the coverage verbosity working.
How Has This Been Tested?
I noticed it was not working when looking at the stdout output after executing
COVERAGE_VERBOSITY=1
.You will see that the messages related to coverage report generation starting with
export coverage using the following format...
always reportverbose: false
before applying this PR.Testing environment:
Types of changes