<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Sep 5, 2015 at 1:40 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 class="">On Sat, Sep 05, 2015 at 01:11:49PM +0530, Raghavendra Talur wrote:<br>
> I started the 10 iteration test today by this patch set<br>
> <a href="http://review.gluster.org/#/c/12109/" rel="noreferrer" target="_blank">http://review.gluster.org/#/c/12109/</a><br>
><br>
> However, it seems no slaves are online for linux. If someone gets to know<br>
> why please update here.<br>
<br>
</span>The Linux slaves always disconnect their Jenkins client and get marked<br>
offline. When tests get started, the Jenkins master connects (ssh) to<br>
the slaves and starts the Jenkins client.<br>
<br>
Is this not happening? You can manually force connecting by clicking on<br>
the hostname of the slave, and then the [Launch slave agent] button.<br></blockquote><div><br></div><div><br></div><div>I did not know about this.<br></div><div>Yes, the slaves did come up after certain time.<br></div><div>Thanks!</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>
HTH,<br>
Niels<br>
</blockquote></div><br></div></div>