Re: [Gluster-infra] Lot of 'centos7-regression' failures

2019-03-07 Thread Michael Scherer
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 Thu, Mar 7, 2019 at 8:09 PM Michael Scherer 
> wrote:
> 
> > 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 with regression-full-run
> > > 
> > > Would be good to resolve sooner, so we can get in many patches
> > > which
> > > are blocking releases.
> > 
> > Can you give a bit more information, like which execution exactly ?
> > 
> > For example:
> > https://build.gluster.org/job/regression-on-demand-full-run/255/ is
> > what you are speaking of ?
> > 
> > (as I do not see the exact string you pointed, I am not sure that's
> > the
> > issue)
> > 
> > --
> > Michael Scherer
> > Sysadmin, Community Infrastructure and Platform, OSAS
> > 
> > 
> > 
-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Lot of 'centos7-regression' failures

2019-03-07 Thread Michael Scherer
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 for now, the others should pick the
work


> On Thu, Mar 7, 2019 at 8:09 PM Michael Scherer 
> wrote:
> 
> > 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 with regression-full-run
> > > 
> > > Would be good to resolve sooner, so we can get in many patches
> > > which
> > > are blocking releases.
> > 
> > Can you give a bit more information, like which execution exactly ?
> > 
> > For example:
> > https://build.gluster.org/job/regression-on-demand-full-run/255/ is
> > what you are speaking of ?
> > 
> > (as I do not see the exact string you pointed, I am not sure that's
> > the
> > issue)
> > 
> > --
> > Michael Scherer
> > Sysadmin, Community Infrastructure and Platform, OSAS
> > 
> > 
> > 
-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Lot of 'centos7-regression' failures

2019-03-07 Thread Deepshikha Khandelwal
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 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 with regression-full-run
> >
> > Would be good to resolve sooner, so we can get in many patches which
> > are blocking releases.
>
> Can you give a bit more information, like which execution exactly ?
>
> For example:
> https://build.gluster.org/job/regression-on-demand-full-run/255/ is
> what you are speaking of ?
>
> (as I do not see the exact string you pointed, I am not sure that's the
> issue)
>
> --
> Michael Scherer
> Sysadmin, Community Infrastructure and Platform, OSAS
>
>
>
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Lot of 'centos7-regression' failures

2019-03-07 Thread Amar Tumballi Suryanarayan
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 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 with regression-full-run
> >
> > Would be good to resolve sooner, so we can get in many patches which
> > are blocking releases.
>
> Can you give a bit more information, like which execution exactly ?
>
> For example:
> https://build.gluster.org/job/regression-on-demand-full-run/255/ is
> what you are speaking of ?
>
> (as I do not see the exact string you pointed, I am not sure that's the
> issue)
>
> --
> Michael Scherer
> Sysadmin, Community Infrastructure and Platform, OSAS
>
>
>

-- 
Amar Tumballi (amarts)
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Lot of 'centos7-regression' failures

2019-03-07 Thread Michael Scherer
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 with regression-full-run
> 
> Would be good to resolve sooner, so we can get in many patches which
> are blocking releases.

Can you give a bit more information, like which execution exactly ?

For example: 
https://build.gluster.org/job/regression-on-demand-full-run/255/ is
what you are speaking of ?

(as I do not see the exact string you pointed, I am not sure that's the
issue)

-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra