Hi Atin, It is not spurious, there is an issue with this pointer I think. All changelog consumers such as bitrot, geo-rep would see this. Since it's a race, it occurred with gsyncd. No, the patch http://review.gluster.org/#/c/10340/ will not take care of it. It just improves the time taken for geo-rep regression. I am looking into it. Thanks and Regards, Kotresh H R ----- Original Message ----- > From: "Atin Mukherjee" <amukherj@xxxxxxxxxx> > To: "kotresh Hiremath Ravishankar" <khiremat@xxxxxxxxxx>, "Aravinda Vishwanathapura Krishna Murthy" > <avishwan@xxxxxxxxxx> > Cc: "Gluster Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Friday, April 24, 2015 9:35:00 AM > Subject: Core by test case : georep-tarssh-hybrid.t > > [1] has core file generated by tests/geo-rep/georep-tarssh-hybrid.t. Is > it something alarming or http://review.gluster.org/#/c/10340/ would take > care of it? > > [1] > http://build.gluster.org/job/rackspace-regression-2GB-triggered/7345/consoleFull > -- > ~Atin > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
