Set QCHECK_MSG_INTERVAL to avoid clutter in CI logs #69
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.
QCheck by default prints updates to stdout often to give the user a sense of progress.
This works well in a terminal/console, but less well in an append-only CI-log where the many printed lines adds clutter.
By setting the environment variable
QCHECK_MSG_INTERVAL
to something more sensible, we obtain cleaner CI logs.(We also use this in
multicoretests
anddomainslib
- but it must have been an oversight inlockfree
)