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/
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.