-
Notifications
You must be signed in to change notification settings - Fork 220
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
Tests are very noisy, 3 #1842
Comments
This looks like working for me
|
My bad, it looks like it is not working. It looks like working locally, but still a lot of logs on CI. |
@emartynov thanks for the suggestion! Yes, you can definitely play around with the logging and either block everything / only expose certain logs / etc..., but that means there is a risk of potentially missing some actual errors. |
True! But this is my compromise from the experience that I never found any error from the paparazzi log, and these logs are producing so much output that it is hard to find which modules test failed. So, I would love to do an experiment where I disable all these logs and see if I'm missing something. |
Hi team!
Description
When running Paparazzi screenshot tests with xml layouts, I constantly get the same STANDARD_ERROR in log outputs that was already mentioned in previous issues.
Note: As suggested, resetting the
LogManager
is a valid workaround, but quite tedious because it has to be done for almost every single test case.Additional information:
Screenshots
See error log above, can provide additional if necessary
The text was updated successfully, but these errors were encountered: