Check interval validity in reconf tests

Without this, if the search part returns min_rate,
then reconf part reports few seconds with a small loss count.

But min_rate means there is a bug or misconfiguration,
so the tests should fail, instead of returning misleading results.

Change-Id: I566608b40ae11d6aaa3fe022a32da97901e1999c
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
(cherry picked from commit 6ac704e7388409c6aa719e50f83d0e08ebd671a0)

diff --git a/resources/libraries/robot/performance/performance_utils.robot b/resources/libraries/robot/performance/performance_utils.robot
index 3f3f41e..2828922 100644 (file)
--- a/resources/libraries/robot/performance/performance_utils.robot
+++ b/resources/libraries/robot/performance/performance_utils.robot
@@ -164,6 +164,8 @@
 | | ... | ${final_trial_duration} | ${initial_trial_duration}
 | | ... | ${number_of_intermediate_phases} | timeout=${timeout}
 | | ... | doublings=${doublings} | traffic_directions=${traffic_directions}
+| | Check NDRPDR interval validity | ${result.pdr_interval}
+| | ... | ${packet_loss_ratio}
 | | Return From Keyword | ${result.pdr_interval.measured_low.transmit_rate}
 
 | Find critical load using PLRsearch