Re: geo-rep regression tests take *ages*?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Just noticed something a bit weird on the regression tests
> for CentOS 6.x:
> 
>   [13:28:44] ./tests/features/weighted-rebalance.t
>   ....................................................... ok       23 s
>   [13:46:50] ./tests/geo-rep/georep-rsync-changelog.t
>   .................................................... ok     1086 s
>   [14:06:53] ./tests/geo-rep/georep-rsync-hybrid.t
>   ....................................................... ok     1203 s
>   [14:08:36] ./tests/geo-rep/georep-setup.t
>   .............................................................. ok      103
>   s
>   [14:26:35] ./tests/geo-rep/georep-tarssh-changelog.t
>   ................................................... ok     1079 s
> 
> That's on:
> 
>   http://build.gluster.org/job/rackspace-regression-2GB-triggered/7285/console
> 
> Those 3x 1000+ second regression tests are adding 56+minutes to the total
> regression test time.
> 
> That's not how it should be is it?

I reported this to the geo-rep team last week.  Apparently it's a low
priority for them, and the tests are so convoluted that I haven't figured
out how to fix it myself.
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux