<div dir="ltr">Looks like the failure is back again. Refer <a href="https://build.gluster.org/job/regression-test-with-multiplex/663/console">https://build.gluster.org/job/regression-test-with-multiplex/663/console</a> and this has been failing in other occurrences too.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 26, 2018 at 2:58 PM, Varsha Rao <span dir="ltr"><<a href="mailto:varao@redhat.com" target="_blank">varao@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Atin,<br>
<span class=""><br>
On Mon, Feb 26, 2018 at 12:18 PM, Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>> wrote:<br>
> Hi Varsha,<br>
><br>
> Thanks for your first feature "namespace" in GlusterFS! As we run a periodic<br>
> regression jobs with brick multiplexing, we have seen that<br>
> tests/basic/namespace.t fails constantly with brick multiplexing enabled. I<br>
> just went through the function check_samples () in the test file and it<br>
> looked to me the function was written with an assumption that every process<br>
> will be associated with one brick instance and will have one log file which<br>
> is not the case for brick multiplexing [1] . If you need further question on<br>
> brick multiplexing, feel free to ask.<br>
<br>
</span>Yes, it was written with that assumption. I will send a patch to fix it.<br>
<br>
Thanks,<br>
Varsha<br>
</blockquote></div><br></div>