[Gluster-devel] Core by test case : georep-tarssh-hybrid.t

[Kotresh Hiremath Ravishankar]

Hi,

I think the following patch fixes the gsyncd core.
http://review.gluster.org/#/c/10366/

The regression has also caught two other racy bugs one in dht
and race between dict_get_bin and dic_set_bin.
Susant and Anuradha will be sending the fixes for them respectively.

Should we wait for these patches to merge and keep geo-rep regression
enabled or should we disable geo-rep regression for now?

Thanks and Regards,
Kotresh H R

----- Original Message -----
> From: "Vijay Bellur" <vbellur at redhat.com>
> To: "Venky Shankar" <vshankar at redhat.com>, gluster-devel at gluster.org, "Kotresh Hiremath Ravishankar"
> <khiremat at redhat.com>
> Sent: Friday, April 24, 2015 2:18:29 PM
> Subject: Re: [Gluster-devel] Core by test case : georep-tarssh-hybrid.t
> 
> On 04/24/2015 10:53 AM, Venky Shankar wrote:
> >
> > On 04/24/2015 10:22 AM, Kotresh Hiremath Ravishankar wrote:
> >> 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.
> >
> > Correct. Jeff has mentioned this a while ago. I'll help out Kotresh in
> > fixing this issue. In the meantime is it possible to disable
> > geo-replication regression test cases until this gets fixed?
> >
> 
> Adding "grep -v geo-rep" with "find ${regression_testsdir}/tests -name
> '*.t'" in run-tests.sh should do this.
> 
> Venky or Kotresh - can one of you do this please?
> 
> We can re-enable geo-rep as soon as we feel confident.
> 
> Thanks,
> Vijay
> 
>