<div dir="ltr"><div><div>Thanks for this patch Jeff.<br><br></div>Helps me to run tests with Brick multiplexing enabled.<br><br></div><div>Instead of manually triggering the run for this patch, as Niels mentioned, it would be good to have a nightly run which will run with a given patch (or patches) and all regressions. Planning to take this as a part of Good Builds effort Nigel is getting done [1].<br><br></div><div>Regards,<br></div><div>Amar<br><br>[1] - <a href="http://lists.gluster.org/pipermail/gluster-devel/2017-March/052245.html">http://lists.gluster.org/pipermail/gluster-devel/2017-March/052245.html</a><br><br></div><div><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 2, 2017 at 2:36 AM, Jeff Darcy <span dir="ltr"><<a href="mailto:jeff@pl.atyp.us" target="_blank">jeff@pl.atyp.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Since the vast majority of our tests run without multiplexing, I'm going<br>
to start running regular runs of all tests with multiplexing turned on.<br>
You can see the patch here:<br>
<br>
<a href="https://review.gluster.org/#/c/17145/" rel="noreferrer" target="_blank">https://review.gluster.org/#/<wbr>c/17145/</a><br>
<br>
There are currently two tests that fail with multiplexing. Note that<br>
these are all tests that passed as of when multiplexing was introduced.<br>
I don't know about these specific tests, but most tests had passed with<br>
multiplexing turned *many times* - sometimes literally over a hundred<br>
because I did more runs that that during development. These are tests<br>
that have been broken since then, because without regular tests the<br>
people making changes could not have known how their changes interact<br>
with multiplexing.<br>
<br>
19:14:41<br>
./tests/bugs/glusterd/bug-<wbr>1367478-volume-start-<wbr>validation-after-glusterd-<wbr>restart.t<br>
..<br>
19:14:41 not ok 17 Got "0" instead of "1", LINENUM:37<br>
19:14:41 FAILED COMMAND: 1 brick_up_status_1 patchy1 127.1.1.2<br>
/d/backends/2/patchy12<br>
<br>
20:52:10 ./tests/features/trash.t ..<br>
20:52:10 not ok 53 Got "2" instead of "1", LINENUM:221<br>
20:52:10 FAILED COMMAND: 1 online_brick_count<br>
20:52:10 ok 54, LINENUM:223<br>
20:52:10 ok 55, LINENUM:226<br>
20:52:10 not ok 56 Got "3" instead of "2", LINENUM:227<br>
20:52:10 FAILED COMMAND: 2 online_brick_count<br>
20:52:10 ok 57, LINENUM:228<br>
20:52:10 ok 58, LINENUM:233<br>
20:52:10 ok 59, LINENUM:236<br>
20:52:10 ok 60, LINENUM:237<br>
20:52:10 not ok 61 , LINENUM:238<br>
20:52:10 FAILED COMMAND: [ -e /mnt/glusterfs/0/abc -a ! -e<br>
/mnt/glusterfs/0/.trashcan ]<br>
<br>
Do we have any volunteers to look into these? I looked at the first one<br>
a bit and didn't find any obvious clues; I haven't looked at the second.<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><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>
</div>