Le jeudi 07 mars 2019 à 20:12 +0530, Deepshikha Khandelwal a écrit :
> Here is one of the console output which Amar is pointing to
> https://build.gluster.org/job/centos7-regression/5051/console
>
> It showed up after we did reboot yesterday only on builder207
Seems 202 also has a issue.
> On
Le jeudi 07 mars 2019 à 20:12 +0530, Deepshikha Khandelwal a écrit :
> Here is one of the console output which Amar is pointing to
> https://build.gluster.org/job/centos7-regression/5051/console
>
> It showed up after we did reboot yesterday only on builder207
ok, so let's put the node offline
Here is one of the console output which Amar is pointing to
https://build.gluster.org/job/centos7-regression/5051/console
It showed up after we did reboot yesterday only on builder207
On Thu, Mar 7, 2019 at 8:09 PM Michael Scherer wrote:
> Le jeudi 07 mars 2019 à 18:47 +0530, Amar Tumballi
https://build.gluster.org/job/regression-on-demand-full-run/ All recent
failures (4-5 of them),
and centos-regression like
https://build.gluster.org/job/centos7-regression/5048/console
On Thu, Mar 7, 2019 at 8:09 PM Michael Scherer wrote:
> Le jeudi 07 mars 2019 à 18:47 +0530, Amar Tumballi
Le jeudi 07 mars 2019 à 18:47 +0530, Amar Tumballi Suryanarayan a
écrit :
> And it is happening with 'failed to determine' the job... anything
> different in jenkins ?
No, we didn't touch to jenkins as far as I know, besides removing nigel
from a group on a github this morning.
> Also happening
And it is happening with 'failed to determine' the job... anything
different in jenkins ?
Also happening with regression-full-run
Would be good to resolve sooner, so we can get in many patches which are
blocking releases.
-Amar
___
Gluster-infra
