Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove spam in pytest output #6620

Merged
merged 10 commits into from
Dec 3, 2021
Merged

Conversation

kozlovsky
Copy link
Contributor

@kozlovsky kozlovsky commented Dec 3, 2021

Currently, pytest output has many unimportant warnings from third-party libraries. We can safely ignore all of them. Displaying all these warnings makes understanding pytest results more complex than necessary. It is essential that if we get some new and important warning one day, we can easily miss it in this wall of existing warnings.

In this PR, I update the pytest.ini config file to suppress all unimportant warnings and also I suppress warnings in code when necessary.

Also, I switched the default logging level in tests from DEBUG to INFO. In most cases, DEBUG output is not helpful, as it mainly consists of spam generated by internal PyQt modules. So, most of the time, it makes test results harder to understand. If necessary, we can always switch it back to DEBUG level later when analyzing some specific test failure.

@kozlovsky kozlovsky requested review from a team, xoriole and devos50 and removed request for a team December 3, 2021 12:46
@kozlovsky kozlovsky marked this pull request as draft December 3, 2021 12:50
@kozlovsky
Copy link
Contributor Author

retest this please

@kozlovsky kozlovsky marked this pull request as ready for review December 3, 2021 13:29
@kozlovsky kozlovsky added this to the 7.12.0 December milestone Dec 3, 2021
xoriole
xoriole previously approved these changes Dec 3, 2021
Copy link
Contributor

@xoriole xoriole left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! 👍

@kozlovsky kozlovsky force-pushed the fix/warnings_in_tests branch 4 times, most recently from eaee228 to b1a0355 Compare December 3, 2021 15:35
@kozlovsky kozlovsky force-pushed the fix/warnings_in_tests branch from b1a0355 to 0ff670e Compare December 3, 2021 15:47
@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 3, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@kozlovsky
Copy link
Contributor Author

retest this please

1 similar comment
@kozlovsky
Copy link
Contributor Author

retest this please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants