aboutsummaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorSiri Hansen <[email protected]>2012-10-10 12:08:55 +0200
committerSiri Hansen <[email protected]>2012-12-14 11:20:55 +0100
commit3f6df2bea5d60264830705f9c663ec7b9286b85f (patch)
treed128293c9e190d15faa208b0ad7088785fd9f54e /lib
parent70892a1e03e441b24f879a9bb5f124defbab2e16 (diff)
downloadotp-3f6df2bea5d60264830705f9c663ec7b9286b85f.tar.gz
otp-3f6df2bea5d60264830705f9c663ec7b9286b85f.tar.bz2
otp-3f6df2bea5d60264830705f9c663ec7b9286b85f.zip
[common_test] Extend valid interval for approximate timer values in tests
When matching the result of tests of timetrap timeouts, the actual time is measured against the expected time, and an interval of +/- 2% was seen as correct result. This turned out to fail on some platforms and is now changed to 5%.
Diffstat (limited to 'lib')
-rw-r--r--lib/common_test/test/ct_test_support.erl4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/common_test/test/ct_test_support.erl b/lib/common_test/test/ct_test_support.erl
index e5e2e68fcb..7aca1fe235 100644
--- a/lib/common_test/test/ct_test_support.erl
+++ b/lib/common_test/test/ct_test_support.erl
@@ -1051,8 +1051,8 @@ result_match({SkipOrFail,{ErrorInd,{EMod,EFunc,{Why,'_'}}}},
true;
result_match({failed,{timetrap_timeout,{'$approx',Num}}},
{failed,{timetrap_timeout,Value}}) ->
- if Value >= trunc(Num-0.02*Num),
- Value =< trunc(Num+0.02*Num) -> true;
+ if Value >= trunc(Num-0.05*Num),
+ Value =< trunc(Num+0.05*Num) -> true;
true -> false
end;
result_match({user_timetrap_error,{Why,'_'}},