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
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
