<div dir="ltr">Super useful. Thanks Nigel (and Amar for the idea).<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 17, 2018 at 12:04 PM, Nigel Babu <span dir="ltr"><<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@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>Hello folks,</div><div><br></div><div>In the past if you had a patch that was fixing a brick multiplex failure, you couldn't test whether it actually fixed brick multiplex failures easily. You had two options:</div><div><br></div><div>* Create a new review where you turn on brick multiplex via the code and also apply your patch. Mark a -1 for this review and iterate until tests passed.<br></div><div>* Merge the patch and pray.</div><div><br></div><div>Now on any patch that you want brick multiplex triggered, just add comment "run brick-mux regression" and it will trigger a run and post results to the review. This is a non-voting job. This should not mess up any votes. Please file a bug if it does.<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888"><div><br>-- <br><div class="m_-2561053911764932426m_-4038773126115115062gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div></font></span></div>
<br>______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br></blockquote></div><br></div>