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
