<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 7, 2018 at 7:38 AM, 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">Hello Atin,<br>
<span class=""><br>
On Tue, Mar 6, 2018 at 10:23 PM, Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>> wrote:<br>
> Looks like the failure is back again. Refer<br>
> <a href="https://build.gluster.org/job/regression-test-with-multiplex/663/console" rel="noreferrer" target="_blank">https://build.gluster.org/job/<wbr>regression-test-with-<wbr>multiplex/663/console</a> and<br>
> this has been failing in other occurrences too.<br>
<br>
</span>Is the core dump file available for this? As on testing locally, the<br>
namespace test does not fail.<br></blockquote><div><br></div><div>The test didn't generate any core. It failed functionally.<br><br><pre class="gmail-console-output"><span class="gmail-timestamp"><b>09:32:12</b> </span>not ok 15 Got "N" instead of "Y", LINENUM:85
<span class="gmail-timestamp"><b>09:32:12</b> </span>FAILED COMMAND: Y check_samples CREATE 28153613 /namespace/foo patchy3</pre><br></div><div>You may have to file a bug under gluster-infrastructure component asking for a machine to debug this further given this is locally not reproducible.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
Varsha<br>
<div class="HOEnZb"><div class="h5"><br>
> On Mon, Feb 26, 2018 at 2:58 PM, Varsha Rao <<a href="mailto:varao@redhat.com">varao@redhat.com</a>> wrote:<br>
>><br>
>> Hi Atin,<br>
>><br>
>> On Mon, Feb 26, 2018 at 12:18 PM, Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>><br>
>> wrote:<br>
>> > Hi Varsha,<br>
>> ><br>
>> > Thanks for your first feature "namespace" in GlusterFS! As we run a<br>
>> > periodic<br>
>> > regression jobs with brick multiplexing, we have seen that<br>
>> > tests/basic/namespace.t fails constantly with brick multiplexing<br>
>> > 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<br>
>> > process<br>
>> > will be associated with one brick instance and will have one log file<br>
>> > which<br>
>> > is not the case for brick multiplexing [1] . If you need further<br>
>> > question on<br>
>> > brick multiplexing, feel free to ask.<br>
>><br>
>> Yes, it was written with that assumption. I will send a patch to fix it.<br>
>><br>
>> Thanks,<br>
>> Varsha<br>
><br>
><br>
</div></div></blockquote></div><br></div></div>