<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 7, 2016 at 4:26 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span>On Thu, Jan 07, 2016 at 03:32:57PM +0530, Raghavendra Talur wrote:<br>
> Hi,<br>
><br>
> I have enabled timeouts for jenkins builds.<br>
> Regression on CentOS and NetBSD now both have a 300 minutes(5 hour) timeout<br>
> and tests will be marked "FAILED" when if it does not complete by then.<br>
<br>
</span>Do you know who is investigating these hangs?<br></blockquote><div><br></div><div>This is already done. Thanks to Manikandan and Raghavendra Gowdappa for</div><div>getting debug info and providing fix respectively.</div><div>Here is the fix <a href="http://review.gluster.org/#/c/13177/">http://review.gluster.org/#/c/13177/</a> and it is already merged.</div><div>Rebase your patches to get them pass on NetBSD.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span><br>
> This is keeping in view the recent hangs which ran tests for more than<br>
> 10-14 hour.<br>
><br>
> Also, the script used in NetBSD does not do any cleanup between runs like<br>
> the CentOS script does.<br>
> I did not modify it for now but we should. Let me know If someone wants to<br>
> take it up. I will have a go at it next week if there are no replies.<br>
<br>
</span>It would be nice to have an extremely simple Jenkins job, that only<br>
executes a script that is located on disk. Could we get such a script in<br>
<a href="https://github.com/gluster/glusterfs-patch-acceptance-tests" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs-patch-acceptance-tests</a> so that we<br>
can easily start running regression tests in the CentOS CI as well?<br></blockquote><div> </div><div>+10</div><div>Some questions:</div><div>1. Currently our images have all the packages baked in, what would be the</div><div>implication if the slaves are fresh CentOS images and need to download the packages</div><div>as part of a ansible playbook?</div><div>2. Instead of regression.sh(in glusterfs-patch-acceptance-tests), run-tests.sh(in glusterfs) is the place where most of the intelligence should reside.</div><div> This would make creating jenkins job much simpler. Thoughts?</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
I would also like to have the Jenkins jobs exported as XML and saved in<br>
the same git repository. That should make it much easier to import the<br>
jobs in other Jenkins environments. Exporting and importing can be done<br>
with the Jenkins CLI, see <a href="http://build.gluster.org/cli" rel="noreferrer" target="_blank">http://build.gluster.org/cli</a> for details.<br></blockquote><div><br></div><div>Awesome idea!!!</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Thanks,<br>
Niels<br>
</blockquote></div><br></div></div>