<p dir="ltr"><br>
On 30 May 2015 16:49, "Niels de Vos" <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
><br>
> Hi all,<br>
><br>
> many of the Jenkins regression-tests have finished before all the smoke<br>
> jobs were done (we have fewer NetBSD slaves and the smoke tests were<br>
> waiting long in the queue). This caused the Verified +1 from the<br>
> regression-tests to be overwritten with Verified=0 once the smoke<br>
> results were available.<br>
><br>
> The configuration change I have made in the several Jenkins jobs that<br>
> are doing smoke testing, is like this:<br>
><br>
> - open a Jenkins job configuration<br>
> - scroll down to "Gerrit trigger"<br>
> - click the [Advanced...] button<br>
> - scroll down to "Gerrit Reporting Values"<br>
> - enable "Skip Vote" for "Successful"<br>
> - click the [Save] button on the bottom of the page<br>
><br>
> This means that any successful result (Verified=0) will not get passed<br>
> on to Gerrit. If the regression test finished before, it will not be<br>
> overwritten anymore. This not-overwriting will be marked in a comment in<br>
> Gerrit with "SUCCESS (skipped)" next to the job. If a smoke test fails,<br>
> the failure will be reported and Verified=-1 gets set.<br>
><br>
> Well, that is the/my theory at least. Let me know if you notice any<br>
I would suggest to have 3 acks, a separate vote id for smoke as well.<br>
> issues.<br>
><br>
> Thanks,<br>
> Niels<br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</p>