chore: Silence Qt warnings during tests #110
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently tests emit a lot of warnings like: Accessing MimeDatabase for text/python before plugins are initialized or SOFT ASSERT [<...>]: "theSettings" in <..>/src/libs/utils/aspects.cpp These make navigating test output difficult. The warnings are mostly useless in tests, so these can be disabled. If this ever becomes a problem, the code can be enhanced to re-enable tests via environment variable.
p12tic
force-pushed
the
test-silence-warning-noise
branch
2 times, most recently
from
a49b685 to
52b6fb2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently tests emit a lot of warnings like:
Accessing MimeDatabase for text/python before plugins are initialized
or
SOFT ASSERT [<...>]: "theSettings" in <..>/src/libs/utils/aspects.cpp
These make navigating test output difficult. The warnings are mostly useless in tests, so these can be disabled.
If this ever becomes a problem, the code can be enhanced to re-enable tests via environment variable.