Re: [Gluster-devel] bug-1432542-mpx-restart-crash.t failing
Thanks Poornima for the analysis. Can someone work on fixing this please? ~Karthik On Fri, Jul 6, 2018 at 3:17 PM Poornima Gurusiddaiah wrote: > The same test case is failing for my patch as well [1]. I requested for a > regression system and tried to reproduce it. > From my analysis, the brick process (mutiplexed) is consuming a lot of > memory, and is being OOM killed. The regression has 1GB ram and the process > is consuming more than 1GB. 1GB for 120 bricks is acceptable considering > there is 1000 threads in that brick process. > Ways to fix: > - Increase the regression system RAM size OR > - Decrease the number of volumes in the test case. > > But what is strange is why the test passes sometimes for some patches. > There could be some bug/? in memory consumption. > > Regards, > Poornima > > > On Fri, Jul 6, 2018 at 2:11 PM, Karthik Subrahmanya > wrote: > >> Hi, >> >> $subject is failing on centos regression for most of the patches with >> timeout error. >> >> 07:32:34 >> >> 07:32:34 [07:33:05] Running tests in file >> ./tests/bugs/core/bug-1432542-mpx-restart-crash.t >> 07:32:34 Timeout set is 300, default 200 >> 07:37:34 ./tests/bugs/core/bug-1432542-mpx-restart-crash.t timed out >> after 300 seconds >> 07:37:34 ./tests/bugs/core/bug-1432542-mpx-restart-crash.t: bad status 124 >> 07:37:34 >> 07:37:34* >> 07:37:34* REGRESSION FAILED * >> 07:37:34* Retrying failed tests in case * >> 07:37:34* we got some spurious failures * >> 07:37:34* >> 07:37:34 >> 07:42:34 ./tests/bugs/core/bug-1432542-mpx-restart-crash.t timed out >> after 300 seconds >> 07:42:34 End of test ./tests/bugs/core/bug-1432542-mpx-restart-crash.t >> 07:42:34 >> >> >> Can anyone take a look? >> >> Thanks, >> Karthik >> >> >> >> ___ >> Gluster-devel mailing list >> Gluster-devel@gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-devel >> > > ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] bug-1432542-mpx-restart-crash.t failing
The same test case is failing for my patch as well [1]. I requested for a regression system and tried to reproduce it. >From my analysis, the brick process (mutiplexed) is consuming a lot of memory, and is being OOM killed. The regression has 1GB ram and the process is consuming more than 1GB. 1GB for 120 bricks is acceptable considering there is 1000 threads in that brick process. Ways to fix: - Increase the regression system RAM size OR - Decrease the number of volumes in the test case. But what is strange is why the test passes sometimes for some patches. There could be some bug/? in memory consumption. Regards, Poornima On Fri, Jul 6, 2018 at 2:11 PM, Karthik Subrahmanya wrote: > Hi, > > $subject is failing on centos regression for most of the patches with > timeout error. > > 07:32:34 > > 07:32:34 [07:33:05] Running tests in file ./tests/bugs/core/bug-1432542- > mpx-restart-crash.t > 07:32:34 Timeout set is 300, default 200 > 07:37:34 ./tests/bugs/core/bug-1432542-mpx-restart-crash.t timed out > after 300 seconds > 07:37:34 ./tests/bugs/core/bug-1432542-mpx-restart-crash.t: bad status 124 > 07:37:34 > 07:37:34* > 07:37:34* REGRESSION FAILED * > 07:37:34* Retrying failed tests in case * > 07:37:34* we got some spurious failures * > 07:37:34* > 07:37:34 > 07:42:34 ./tests/bugs/core/bug-1432542-mpx-restart-crash.t timed out > after 300 seconds > 07:42:34 End of test ./tests/bugs/core/bug-1432542-mpx-restart-crash.t > 07:42:34 > > > Can anyone take a look? > > Thanks, > Karthik > > > > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] bug-1432542-mpx-restart-crash.t failing
Hi, $subject is failing on centos regression for most of the patches with timeout error. 07:32:34 07:32:34 [07:33:05] Running tests in file ./tests/bugs/core/bug-1432542-mpx-restart-crash.t 07:32:34 Timeout set is 300, default 200 07:37:34 ./tests/bugs/core/bug-1432542-mpx-restart-crash.t timed out after 300 seconds 07:37:34 ./tests/bugs/core/bug-1432542-mpx-restart-crash.t: bad status 124 07:37:34 07:37:34* 07:37:34* REGRESSION FAILED * 07:37:34* Retrying failed tests in case * 07:37:34* we got some spurious failures * 07:37:34* 07:37:34 07:42:34 ./tests/bugs/core/bug-1432542-mpx-restart-crash.t timed out after 300 seconds 07:42:34 End of test ./tests/bugs/core/bug-1432542-mpx-restart-crash.t 07:42:34 Can anyone take a look? Thanks, Karthik ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
