<div dir="ltr"><div dir="ltr"><div dir="ltr"><a href="https://build.gluster.org/job/regression-on-demand-full-run/">https://build.gluster.org/job/regression-on-demand-full-run/</a> All recent failures (4-5 of them), <br></div><div dir="ltr"><br></div><div>and centos-regression like <a href="https://build.gluster.org/job/centos7-regression/5048/console">https://build.gluster.org/job/centos7-regression/5048/console</a></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 7, 2019 at 8:09 PM Michael Scherer <<a href="mailto:mscherer@redhat.com">mscherer@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Le jeudi 07 mars 2019 à 18:47 +0530, Amar Tumballi Suryanarayan a<br>
écrit :<br>
> And it is happening with 'failed to determine' the job... anything<br>
> different in jenkins ?<br>
<br>
No, we didn't touch to jenkins as far as I know, besides removing nigel<br>
from a group on a github this morning.<br>
<br>
> Also happening with regression-full-run<br>
> <br>
> Would be good to resolve sooner, so we can get in many patches which<br>
> are blocking releases.<br>
<br>
Can you give a bit more information, like which execution exactly ?<br>
<br>
For example: <br>
<a href="https://build.gluster.org/job/regression-on-demand-full-run/255/" rel="noreferrer" target="_blank">https://build.gluster.org/job/regression-on-demand-full-run/255/</a> is<br>
what you are speaking of ?<br>
<br>
(as I do not see the exact string you pointed, I am not sure that's the<br>
issue)<br>
<br>
-- <br>
Michael Scherer<br>
Sysadmin, Community Infrastructure and Platform, OSAS<br>
<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>