[LRUG] scrolling through long testing logs to find errors from CI on PRs

[Samuel Joseph]

Hi LRugers,

Hope everyone is well.  I was wondering if anyone else found themselves 
getting exhausted scrolling through long testing logs to find errors 
from CI on PRs?  All the CI systems we've used so far are great at 
providing a link to the complete CI output in a PR, but it always seems 
to take a fair few minutes to get through the CI logs to find the actual 
error message that will then allow us to debug the issue.

Does anyone know of a clever CI system that is smart enough to rake the 
relevant error message (from the few failing tests) and post that 
directly into a GitHub PR or similar in order to speed up the process of 
analysis?

Many thanks in advance

Best, Sam