The Metron build logs contain a great deal of information, including a large 
number of warnings / exceptions that do not result in test failures but still 
fill the log.  This makes troubleshooting test/build issues difficult.  For 
example - the travis ci log for PR #276’s recent failure doesn’t even have the 
final errors because the log is too long.

What are some things that can be done to make the situation better?


Reply via email to