Bug 1373241

Summary:	The new strfmt_errors Jenkins job gets triggered 2x, sometimes
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, nigelb
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-06 05:05:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Niels de Vos 2016-09-05 15:11:33 UTC

Description of problem:
Sometimes(?) when new patches get posted, the new strfmt_errors job gets triggered 2x. This is probably not intentional :)

Version-Release number of selected component (if applicable):
Todays jenkins configuration

How reproducible:
Post a patch (and be lucky?)

Steps to Reproduce:
1. write code
2. commit to local repo
3. run ./rfc.sh

Actual results:
Tests start to run.

Expected results:
Tests start to run, but more than once.

Additional info:
See the left side of https://build.gluster.org/job/strfmt_errors/

Comment 1 Nigel Babu 2016-09-06 05:05:31 UTC

There were several things wrong here. The root case of the bug is I didn't specify a gerrit-server. We have two servers defined, so it was picking up review.gluster.org and review.gluster.org_for_smoke. The fix - https://github.com/gluster/glusterfs-patch-acceptance-tests/commit/89551cbc91e4ebc77490cced54e3a676ff81cdb1

This also caused an additional bug. It was voting on patches which it shouldn't have been voting yet. The intention was to turn on voting once all branches are green. That issue should also be fixed now.