<div dir="ltr">Ok, RCA:<div><br></div><div>In NetBSD cores are being generated in /d/backends/*/*.core</div><div>run-tests.sh looks only for "/core*" when looking for cores.</div><div><br></div><div>So, at the end of test run when regression.sh looks for core everywhere, it finds one and errors out.</div><div><br></div><div>Should think of a solution which is generic. Will update.</div><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 28, 2016 at 11:37 AM, Raghavendra Talur <span dir="ltr"><<a href="mailto:rtalur@redhat.com" target="_blank">rtalur@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"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Jan 28, 2016 at 11:17 AM, Atin Mukherjee <span dir="ltr"><<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>></span> wrote:<br></span><span class=""><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">Are we running a different version of run-tests.sh in jenkin slaves. The<br>
reason of suspection is beacuse in last couple of runs [1] & [2] in<br>
NetBSD I am seeing no failures apart from bad tests but the regression<br>
voted failure and I can not make out any valid reason out of it.<br>
<br>
[1]<br>
<a href="https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13756/consoleFull" rel="noreferrer" target="_blank">https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13756/consoleFull</a><br>
[2]<br>
<a href="https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13755/consoleFull" rel="noreferrer" target="_blank">https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13755/consoleFull</a></blockquote><div><br></div><div><br></div></span><span class=""><div><div>I checked the slave machine now.</div><div>regression.sh file is different but the run-tests.sh script is same. </div><div><br></div><div>A wild guess here, is it possible that the core generation takes time and when we check for a core right after a test is run it is not present yet?</div><div>Does anyone know how to work around that?</div></div><div><br></div></span><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>
<br><span class="">
~Atin<br>
_______________________________________________<br>
Gluster-infra mailing list<br>
<a href="mailto:Gluster-infra@gluster.org" target="_blank">Gluster-infra@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-infra" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-infra</a><br>
</span></blockquote></div><br></div></div>
</blockquote></div><br></div></div></div>