Lower Chasing_The_Leader rate threshold

With the rate threshold set at 50, this
test fails frequently. Not sure why that
threshold was picked but lowered it to 10.
Looking at past runs, the actual rate
fluctuates anywhere between 20-80, which is
indicative of the unpredictablity of load in
the CS environment as the related
production code is mostly network I/O bound.

Change-Id: Id579c9553e0e48c85c039de5fddb0d1e56a5f2e6
Signed-off-by: Tom Pantelis <tompantelis@gmail.com>

diff --git a/csit/suites/controller/cluster_singleton/chasing_the_leader.robot b/csit/suites/controller/cluster_singleton/chasing_the_leader.robot
index fcdc5b8f675a0ac011d6a2a8de677f56c07f4de1..ad7620b4beb00defe7ac9bc6c4b115aff6c5cf78 100644 (file)
--- a/csit/suites/controller/cluster_singleton/chasing_the_leader.robot
+++ b/csit/suites/controller/cluster_singleton/chasing_the_leader.robot
@@ -21,7 +21,7 @@ Resource          ${CURDIR}/../../../libraries/SetupUtils.robot
 
 *** Variables ***
 ${TEST_DURATION}    1m
-${ACCEPTED_PER_SEC_RATE}    50
+${ACCEPTED_PER_SEC_RATE}    10
 # TODO: Use a better wait to start testing when ODL does not use CPU for initializing features. Then inrease rate to 100.
 
 *** Test Cases ***