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

[Ed James]

Sam > which CI systems have you used so far? That would probably help to get some more specific guidance on which CI platform(s) to try which could give you what you need.


       	Ed James 
I will respect your spam <mailto:ed.james.spam at gmail.com>

> On 27 Feb 2019, at 09:58, Samuel Joseph <tansaku at gmail.com> wrote:
> 
> 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
> 
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> Archives: http://lists.lrug.org/pipermail/chat-lrug.org
> Manage your subscription: http://lists.lrug.org/options.cgi/chat-lrug.org
> List info: http://lists.lrug.org/listinfo.cgi/chat-lrug.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20190227/ad976882/attachment-0001.html>