<div dir="ltr">Replies inline<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 26, 2018 at 1:48 AM Shyam Ranganathan <<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 07/24/2018 03:28 PM, Shyam Ranganathan wrote:<br>
> On 07/24/2018 03:12 PM, Shyam Ranganathan wrote:<br>
>> 1) master branch health checks (weekly, till branching)<br>
>> - Expect every Monday a status update on various tests runs<br>
> <br>
> See <a href="https://build.gluster.org/job/nightly-master/" rel="noreferrer" target="_blank">https://build.gluster.org/job/nightly-master/</a> for a report on<br>
> various nightly and periodic jobs on master.<br>
> <br>
> RED:<br>
> 1. Nightly regression<br>
> 2. Regression with multiplex (cores and test failures)<br>
> 3. line-coverage (cores and test failures)<br>
<br>
The failures for line coverage issues, are filed as the following BZs<br>
1) Parent BZ for nightly line coverage failure:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1608564" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1608564</a><br>
<br>
2) glusterd crash in test sdfs-sanity.t:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1608566" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1608566</a><br>
<br>
glusterd folks, request you to take a look to correct this.<br>
<br>
3) bug-1432542-mpx-restart-crash.t times out consistently:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1608568" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1608568</a><br>
<br>
@nigel is there a way to on-demand request lcov tests through gerrit? I<br>
am thinking of pushing a patch that increases the timeout and check if<br>
it solves the problem for this test as detailed in the bug.<br></blockquote><div><br></div><div>You should have access to trigger the job from Jenkins. Does that work for now?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> <br>
> Calling out to contributors to take a look at various failures, and post<br>
> the same as bugs AND to the lists (so that duplication is avoided) to<br>
> get this to a GREEN status.<br>
> <br>
> GREEN:<br>
> 1. cpp-check<br>
> 2. RPM builds<br>
> <br>
> IGNORE (for now):<br>
> 1. clang scan (@nigel, this job requires clang warnings to be fixed to<br>
> go green, right?)<br></blockquote><div><br></div><div>So there are two ways. Back when I first ran it, I set a limit on how many clang failures we have. If we went above the number, the job would turn yellow. The current threshold is 955 and we're at 1001. What would be useful is for us to fix a few bugs a week and keeping bumping this limit down.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> <br>
> Shyam<br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
> <a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
> <br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="m_-6320190438273518818gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div></div>