On 07/27/2013 08:50 AM, Anand Avati wrote:
The same test seems to finish in ~ 12s on my laptop:
# prove --timer ./tests/bugs/bug-821056.t
[11:34:17] ./tests/bugs/bug-821056.t .. ok 12264 ms
Well, it seems to be stemming from patch 5376 as per jenkins:
http://build.gluster.org/job/regression/1769/console
I consistently get this result on my laptop:
[root@deepthought glusterfs.git]# prove --timer ./tests/bugs/bug-821056.t
[09:10:58] ./tests/bugs/bug-821056.t .. ok 1220937 ms
[09:31:19]
All tests successful.
Files=1, Tests=22, 1222 wallclock secs ( 0.05 usr 0.00 sys + 0.92 cusr
0.67 csys = 1.64 CPU)
Result: PASS
A lot of the recent regression test runs in jenkins does show
bug-821056.t to be taking around 1040+ seconds.
-Vijay
On Fri, Jul 26, 2013 at 12:55 PM, Vijay Bellur <vbel...@redhat.com
<mailto:vbel...@redhat.com>> wrote:
After patch 5111 got merged, 821056.t seems to take about 17+
minutes. Do we know why?
[11:31:54] ./tests/bugs/bug-821056.t ......................... ok
1046 s
Thanks,
Vijay
_________________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org <mailto:Gluster-devel@nongnu.org>
https://lists.nongnu.org/__mailman/listinfo/gluster-devel
<https://lists.nongnu.org/mailman/listinfo/gluster-devel>
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
