<div dir="ltr">We discussed reducing the number of volumes in the maintainers' meeting.Should we still go ahead and do that?<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 July 2018 at 15:45, Xavi Hernandez <span dir="ltr"><<a href="mailto:jahernan@redhat.com" target="_blank">jahernan@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 class="gmail_quote"><span class=""><div dir="ltr">On Mon, Jul 9, 2018 at 11:14 AM Karthik Subrahmanya <<a href="mailto:ksubrahm@redhat.com" target="_blank">ksubrahm@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Deepshikha,<div><br></div><div>Are you looking into this failure? I can still see this happening for all the regression runs.</div></div></blockquote><div><br></div></span><div>I've executed the failing script on my laptop and all tests finish relatively fast. What seems to take time is the final cleanup. I can see 'semanage' taking some CPU during destruction of volumes. The test required 350 seconds to finish successfully.</div><div><br></div><div>Not sure what caused the cleanup time to increase, but I've created a bug [1] to track this and a patch [2] to give more time to this test. This should allow all blocked regressions to complete successfully.</div><div><br></div><div>Xavi</div><div><br></div><div>[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1599250" target="_blank">https://bugzilla.redhat.<wbr>com/show_bug.cgi?id=1599250</a></div>[2] <a href="https://review.gluster.org/20482" target="_blank">https://review.gluster.org/<wbr>20482</a></div><div><div class="h5"><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Thanks & Regards,</div><div>Karthik</div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Jul 8, 2018 at 7:18 AM Atin Mukherjee <<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><a href="https://build.gluster.org/job/regression-test-with-multiplex/794/display/redirect" target="_blank">https://build.gluster.org/job/<wbr>regression-test-with-<wbr>multiplex/794/display/redirect</a> has the same test failing. Is the reason of the failure different given this is on jenkins?</div></div><div><br><div class="gmail_quote"><div dir="ltr">On Sat, 7 Jul 2018 at 19:12, Deepshikha Khandelwal <<a href="mailto:dkhandel@redhat.com" target="_blank">dkhandel@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi folks,<br>
<br>
The issue[1] has been resolved. Now the softserve instance will be<br>
having 2GB RAM i.e. same as that of the Jenkins builder's sizing<br>
configurations.<br>
<br>
[1] <a href="https://github.com/gluster/softserve/issues/40" rel="noreferrer" target="_blank">https://github.com/gluster/<wbr>softserve/issues/40</a><br>
<br>
Thanks,<br>
Deepshikha Khandelwal<br>
<br>
On Fri, Jul 6, 2018 at 6:14 PM, Karthik Subrahmanya <<a href="mailto:ksubrahm@redhat.com" target="_blank">ksubrahm@redhat.com</a>> wrote:<br>
><br>
><br>
> On Fri 6 Jul, 2018, 5:18 PM Deepshikha Khandelwal, <<a href="mailto:dkhandel@redhat.com" target="_blank">dkhandel@redhat.com</a>><br>
> wrote:<br>
>><br>
>> Hi Poornima/Karthik,<br>
>><br>
>> We've looked into the memory error that this softserve instance have<br>
>> showed up. These machine instances have 1GB RAM which is not in the<br>
>> case with the Jenkins builder. It's 2GB RAM there.<br>
>><br>
>> We've created the issue [1] and will solve it sooner.<br>
><br>
> Great. Thanks for the update.<br>
>><br>
>><br>
>> Sorry for the inconvenience.<br>
>><br>
>> [1] <a href="https://github.com/gluster/softserve/issues/40" rel="noreferrer" target="_blank">https://github.com/gluster/<wbr>softserve/issues/40</a><br>
>><br>
>> Thanks,<br>
>> Deepshikha Khandelwal<br>
>><br>
>> On Fri, Jul 6, 2018 at 3:44 PM, Karthik Subrahmanya <<a href="mailto:ksubrahm@redhat.com" target="_blank">ksubrahm@redhat.com</a>><br>
>> wrote:<br>
>> > Thanks Poornima for the analysis.<br>
>> > Can someone work on fixing this please?<br>
>> ><br>
>> > ~Karthik<br>
>> ><br>
>> > On Fri, Jul 6, 2018 at 3:17 PM Poornima Gurusiddaiah<br>
>> > <<a href="mailto:pgurusid@redhat.com" target="_blank">pgurusid@redhat.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> The same test case is failing for my patch as well [1]. I requested for<br>
>> >> a<br>
>> >> regression system and tried to reproduce it.<br>
>> >> From my analysis, the brick process (mutiplexed) is consuming a lot of<br>
>> >> memory, and is being OOM killed. The regression has 1GB ram and the<br>
>> >> process<br>
>> >> is consuming more than 1GB. 1GB for 120 bricks is acceptable<br>
>> >> considering<br>
>> >> there is 1000 threads in that brick process.<br>
>> >> Ways to fix:<br>
>> >> - Increase the regression system RAM size OR<br>
>> >> - Decrease the number of volumes in the test case.<br>
>> >><br>
>> >> But what is strange is why the test passes sometimes for some patches.<br>
>> >> There could be some bug/? in memory consumption.<br>
>> >><br>
>> >> Regards,<br>
>> >> Poornima<br>
>> >><br>
>> >><br>
>> >> On Fri, Jul 6, 2018 at 2:11 PM, Karthik Subrahmanya<br>
>> >> <<a href="mailto:ksubrahm@redhat.com" target="_blank">ksubrahm@redhat.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> Hi,<br>
>> >>><br>
>> >>> $subject is failing on centos regression for most of the patches with<br>
>> >>> timeout error.<br>
>> >>><br>
>> >>> 07:32:34<br>
>> >>><br>
>> >>> ==============================<wbr>==============================<wbr>====================<br>
>> >>> 07:32:34 [07:33:05] Running tests in file<br>
>> >>> ./tests/bugs/core/bug-1432542-<wbr>mpx-restart-crash.t<br>
>> >>> 07:32:34 Timeout set is 300, default 200<br>
>> >>> 07:37:34 ./tests/bugs/core/bug-1432542-<wbr>mpx-restart-crash.t timed out<br>
>> >>> after 300 seconds<br>
>> >>> 07:37:34 ./tests/bugs/core/bug-1432542-<wbr>mpx-restart-crash.t: bad status<br>
>> >>> 124<br>
>> >>> 07:37:34<br>
>> >>> 07:37:34 ******************************<wbr>***<br>
>> >>> 07:37:34 * REGRESSION FAILED *<br>
>> >>> 07:37:34 * Retrying failed tests in case *<br>
>> >>> 07:37:34 * we got some spurious failures *<br>
>> >>> 07:37:34 ******************************<wbr>***<br>
>> >>> 07:37:34<br>
>> >>> 07:42:34 ./tests/bugs/core/bug-1432542-<wbr>mpx-restart-crash.t timed out<br>
>> >>> after 300 seconds<br>
>> >>> 07:42:34 End of test ./tests/bugs/core/bug-1432542-<wbr>mpx-restart-crash.t<br>
>> >>> 07:42:34<br>
>> >>><br>
>> >>> ==============================<wbr>==============================<wbr>====================<br>
>> >>><br>
>> >>> Can anyone take a look?<br>
>> >>><br>
>> >>> Thanks,<br>
>> >>> Karthik<br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> ______________________________<wbr>_________________<br>
>> >>> Gluster-devel mailing list<br>
>> >>> <a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
>> >>> <a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
>> >><br>
>> >><br>
>> ><br>
>> > ______________________________<wbr>_________________<br>
>> > Gluster-infra mailing list<br>
>> > <a href="mailto:Gluster-infra@gluster.org" target="_blank">Gluster-infra@gluster.org</a><br>
>> > <a href="https://lists.gluster.org/mailman/listinfo/gluster-infra" rel="noreferrer" target="_blank">https://lists.gluster.org/<wbr>mailman/listinfo/gluster-infra</a><br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="m_-7009236854911016900gmail-m_8038808095630511528m_-4859419650416721006gmail_signature">- Atin (atinm)</div>
</blockquote></div>
______________________________<wbr>_________________<br>
Gluster-infra mailing list<br>
<a href="mailto:Gluster-infra@gluster.org" target="_blank">Gluster-infra@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-infra" rel="noreferrer" target="_blank">https://lists.gluster.org/<wbr>mailman/listinfo/gluster-infra</a></blockquote></div></div></div></div>
<br>______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br></blockquote></div><br></div>