[Gluster-devel] rebase + regression run voting

Nigel Babu nigelb at redhat.com
Tue Aug 2 15:23:31 UTC 2016


Ah, that's an edge case. Retrigger them. I think as a future note, if
you're going to edit the commit or do a no-op rebase, do it after your
regression results are in.

On Tue, Aug 2, 2016 at 8:22 PM, Pranith Kumar Karampuri <pkarampu at redhat.com
> wrote:

> hi Nigel,
>        When we rebase the patch by just changing the
> commit-message/description it rightly doesn't re-trigger the regression,
> but the regression results are still coming for patchset before rebase so
> the +1s are not appearing. You can see
> http://review.gluster.org/#/c/15070/ as an example. Is there a way to
> give +1s now for the patch or shall I retrigger the runs?
>
> --
> Pranith
>



-- 
nigelb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20160802/172427c4/attachment.html>


More information about the Gluster-devel mailing list