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

[Samuel Joseph]

Hi Ed,

We use travis and semaphore most extensively, but also some CircleCI 
although we clearly haven't taken advantage of everything offered there 
yet, so much explore further.  This is the usual representation of build 
failure we get from, say, Semaphore:


clicking through on details takes us to:

a click opens to this


and then another click to see the full test log:

In this particular case with a lot of errors and the second cuke run of 
failures the relevent error messages are easy to find.  And Semaphore 
output is easier to navigate than travis I find.  But each of these 
clicks takes time to load, and more often than not, there is fairly big 
amount of scrolling to get to the load bearing error message.

Also, we are working with a lot of learning developers who are not 
necessarily familiar with CI and in reviewing their pull requests what I 
find myself doing is navigating in there for them, and copying and 
pasting the relevant error messages into the PR so they can get to work 
on the issue, so if that could be at least partially automated I feel 
like that could save a lot of time and help a lot of up and coming 
developers ...

Best, Sam



On 27/02/2019 10:18, Ed James wrote:
> 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 
>> <mailto: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 <mailto: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
>
>
> _______________________________________________
> 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/20190301/a6d33ea6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nggidjfomdbkpcmi.png
Type: image/png
Size: 209653 bytes
Desc: not available
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20190301/a6d33ea6/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hpidkflbegihmoak.png
Type: image/png
Size: 60611 bytes
Desc: not available
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20190301/a6d33ea6/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dpobpmkonioeobmd.png
Type: image/png
Size: 128593 bytes
Desc: not available
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20190301/a6d33ea6/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gaaedoaajlopchbo.png
Type: image/png
Size: 331126 bytes
Desc: not available
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20190301/a6d33ea6/attachment-0003.png>