<div dir="ltr">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.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 2, 2016 at 8:22 PM, Pranith Kumar Karampuri <span dir="ltr"><<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>hi Nigel,<br></div> 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 <a href="http://review.gluster.org/#/c/15070/" target="_blank">http://review.gluster.org/#/c/15070/</a> as an example. Is there a way to give +1s now for the patch or shall I retrigger the runs?<span class="HOEnZb"><font color="#888888"><br clear="all"><div><div><br>-- <br><div data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div></font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div>