On Wed, Jan 13, 2016 at 04:40:36PM +0530, Raghavendra Talur wrote: > On Wed, Jan 13, 2016 at 2:35 PM, Niels de Vos <ndevos@xxxxxxxxxx> wrote: > > > On Wed, Jan 13, 2016 at 09:56:54AM +0530, Atin Mukherjee wrote: > > > Hi Raghavendra, > > > > > > I noticed that for the below patches Gluster Build system hasn't voted > > > and hence the verified flag doesn't have an ack from it even if the > > > regression has passed. I think something is fishy in the script now, > > > mind having a look? > > > > > > http://review.gluster.org/#/c/13222/ > > > http://review.gluster.org/#/c/13210/ > > > > I've manually approved these now. No idea what caused the voting to have > > failed. The votes are done through an ssh command in the regression test > > itself, it is not a property of the test job (which is an option, but > > gives us less flexibility). > > > > Maybe someone can figure out what went wrong? I could not see anything > > in the console log that suggested a problem. > > > > I checked the console logs and jenkins log from UI. I did not see any error > being reported. > The commands use by NetBSD and Linux Regression are same too with different > user names. > > I guess something is wrong with how Gerrit interprets it. > Someone please check Gerrit logs, I don't know where to check. I copy/pasted that command and executed it, worked just fine. Maybe Gerrit was unavailable at the time the Jenkins job tried to set the Verified result? Niels
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
