<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Ed,</p>
<p>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:<br>
<br>
</p>
<p><img src="cid:part1.224D6221.9672116A@gmail.com" alt=""
width="636" height="316"></p>
<p><br>
</p>
<p>clicking through on details takes us to:<br>
<br>
<img src="cid:part2.2EE73011.308FA177@gmail.com" alt=""
width="759" height="156"></p>
<p>a click opens to this</p>
<p><img src="cid:part3.E645CDD6.AA89B073@gmail.com" alt=""
width="822" height="269"><br>
and then another click to see the full test log:<br>
<br>
<img src="cid:part4.9AE1D4F0.53270C6B@gmail.com" alt=""
width="689" height="155"></p>
<p>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.</p>
<p>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 ...</p>
<p>Best, Sam<br>
</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 27/02/2019 10:18, Ed James wrote:<br>
</div>
<blockquote type="cite"
cite="mid:B700B9F9-89C3-4DA4-8D69-CC88FD12DBB0@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
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.<br class="">
<div class="">
<br class="">
<hr style="display: block; height: 1px; border: 0; border-top:
1px dotted #ccc; margin: 5px 0; padding: 0;" class="">
<br class="">
<table class="" width="100%" cellpadding="0" border="0">
<tbody class="">
<tr class="">
<td class="" width="70" valign="top"> <img
src="http://ej-public.s3.amazonaws.com/images/rubbish.png"
style="margin: 8px 8px 0 0;" class=""
moz-do-not-send="true" height="60"> </td>
<td style="font-family:'Lucida Grande',sans-serif"
class=""> <span style="font-weight:bold; color:
#333333; font-size: 18px; line-height:30px;" class="">Ed
James</span> <br class="">
<span style="font-weight:normal; color: #999; font-size:
12px; line-height:16px;" class=""> <a
href="mailto:ed.james.spam@gmail.com"
style="color:#999; text-decoration:none"
target="_blank" class="" moz-do-not-send="true">I
will respect your spam</a> </span> </td>
</tr>
</tbody>
</table>
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 27 Feb 2019, at 09:58, Samuel Joseph <<a
href="mailto:tansaku@gmail.com" class=""
moz-do-not-send="true">tansaku@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi LRugers,<br class="">
<br class="">
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.<br class="">
<br class="">
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?<br
class="">
<br class="">
Many thanks in advance<br class="">
<br class="">
Best, Sam<br class="">
<br class="">
_______________________________________________<br
class="">
Chat mailing list<br class="">
<a href="mailto:Chat@lists.lrug.org" class=""
moz-do-not-send="true">Chat@lists.lrug.org</a><br
class="">
Archives: <a class="moz-txt-link-freetext" href="http://lists.lrug.org/pipermail/chat-lrug.org">http://lists.lrug.org/pipermail/chat-lrug.org</a><br
class="">
Manage your subscription:
<a class="moz-txt-link-freetext" href="http://lists.lrug.org/options.cgi/chat-lrug.org">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br
class="">
List info:
<a class="moz-txt-link-freetext" href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br
class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Chat mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a>
Archives: <a class="moz-txt-link-freetext" href="http://lists.lrug.org/pipermail/chat-lrug.org">http://lists.lrug.org/pipermail/chat-lrug.org</a>
Manage your subscription: <a class="moz-txt-link-freetext" href="http://lists.lrug.org/options.cgi/chat-lrug.org">http://lists.lrug.org/options.cgi/chat-lrug.org</a>
List info: <a class="moz-txt-link-freetext" href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a>
</pre>
</blockquote>
</body>
</html>