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

[James Turley]

I wonder if this is actually a CI issue? Ie, I would want my testing tools
not to be enormously noisy in the logs, but only create output that helps
to debug issues.

CircleCI allows you to break down your pipeline into very small chunks and
will create a status for each of them so you can go directly to the one
that failed - maybe give that a try?

James

On Wed, 27 Feb 2019, 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/203d1187/attachment-0001.html>