Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
In case of errors (especially flakey test cases) which most often appear on Travis, it would be helpful to log the error messages in order to detect the actual problem. Since we also have test exceptions which would be logged the same way and we don't want to clutter the logs, we would have to set up the logging for the individual classes selectively.
What do you think?