summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPranith Kumar K <pkarampu@redhat.com>2013-01-25 19:23:15 +0530
committerAnand Avati <avati@redhat.com>2013-01-28 18:45:11 -0800
commit15716cfe7a38dc1a49fde298d84c9efdb7617ada (patch)
tree3e4d966ff11c34ebfeb598a0936bf335cd98708e
parentfd9612466a8dfbfe0f918426919cf8ec135ffb4b (diff)
Tests: Fix latency calculation
Idea is to make sure that the FINODELK max latency is not in the order of seconds. Change-Id: Ic47dc46c3b2d24d223fe7e2212c4c035de37c9ae BUG: 895235 Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: http://review.gluster.org/4434 Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com>
-rw-r--r--tests/bugs/bug-895235.t7
1 files changed, 4 insertions, 3 deletions
diff --git a/tests/bugs/bug-895235.t b/tests/bugs/bug-895235.t
index a9f176a76..b0a92c92f 100644
--- a/tests/bugs/bug-895235.t
+++ b/tests/bugs/bug-895235.t
@@ -13,9 +13,10 @@ TEST $CLI volume set $V0 cluster.eager-lock off
TEST $CLI volume start $V0
TEST glusterfs --entry-timeout=0 --attribute-timeout=0 -s $H0 --volfile-id=$V0 $M0 --direct-io-mode=enable
-T=$(date +%s)
+TEST gluster volume profile $V0 start
TEST dd of=$M0/a if=/dev/zero bs=1M count=1 oflag=append
-T1=$(date +%s)
-EXPECT "0" echo "$(($T1-$T))"
+finodelk_max_latency=$($CLI volume profile $V0 info | grep FINODELK | awk 'BEGIN {max = 0} {if ($6 > max) max=$6;} END {print max}' | cut -d. -f 1 | egrep "[0-9]{7,}")
+
+TEST [ -z $finodelk_max_latency ]
cleanup;