Re: [Gluster-infra] Disabling nbslave72

[Kaushal M]

None of the tests cast any vote. The vote is cast by an ssh command at
the end of the test script. The script itself wasn't started as the
slave couldn't be reached.

The failures were only displayed in jenkins.

On Thu, May 7, 2015 at 12:15 PM, Emmanuel Dreyfus m...@netbsd.org wrote:
 Kaushal M kshlms...@gmail.com wrote:

 This seems like a network issue to me. Jenkins is not able to connect
 to the slave to start the job, and hence is marking the job as a
 failure. But it doesn't seem to be affecting all the slaves though.

 But the gerrit vote is cast using a key on the slave, which means it
 must be able to connect.

 --
 Emmanuel Dreyfus
 http://hcpnet.free.fr/pubz
 m...@netbsd.org
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Disabling nbslave72

[Emmanuel Dreyfus]

Kaushal M kshlms...@gmail.com wrote:

 nbslave72 just caused a bunch of netbsd (~40) regressions jobs to just
 fail. I'm disabling it for now, and will retrigger the tests as much
 as possible.

We have seen this on other NetBSD VM recently. Restoring from image did
not fix the problem. My understanding is that this is the jenkins side
that is screwed. 

Justin, we experienced similar troubles in the past, how did you fix
them?



-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra