aboutsummaryrefslogtreecommitdiffstats
path: root/lib/sasl
diff options
context:
space:
mode:
authorSiri Hansen <[email protected]>2012-12-19 09:51:57 +0100
committerSiri Hansen <[email protected]>2013-01-25 15:28:17 +0100
commit81e3fd3127298b84e13e8d462918faa2cc1f7c6e (patch)
tree6c0e0bd205e13e17511d5b8fe3b89c9c7ea3b7b6 /lib/sasl
parent331833c95a215987884165fa07461b6d9353ad4c (diff)
downloadotp-81e3fd3127298b84e13e8d462918faa2cc1f7c6e.tar.gz
otp-81e3fd3127298b84e13e8d462918faa2cc1f7c6e.tar.bz2
otp-81e3fd3127298b84e13e8d462918faa2cc1f7c6e.zip
Fix release_handler_SUITE:otp_9395_check_old_code
This test often fails dues to too high expectations. Don't expect the test to be more than 1000 times faster with no old code - it just doesn't happen!
Diffstat (limited to 'lib/sasl')
-rw-r--r--lib/sasl/test/release_handler_SUITE.erl6
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/sasl/test/release_handler_SUITE.erl b/lib/sasl/test/release_handler_SUITE.erl
index 94cffc988d..82b7a738bb 100644
--- a/lib/sasl/test/release_handler_SUITE.erl
+++ b/lib/sasl/test/release_handler_SUITE.erl
@@ -938,7 +938,7 @@ otp_9417(cleanup,_Conf) ->
%% OTP-9395 - performance problems when there are MANY processes
%% Test that the procedure of checking for old code before an upgrade
-%% can be started is "very much faster" when there is no old code in
+%% can be started is faster when there is no old code in
%% the system.
otp_9395_check_old_code(Conf) when is_list(Conf) ->
@@ -978,8 +978,8 @@ otp_9395_check_old_code(Conf) when is_list(Conf) ->
"\tAfter purge: ~.2f sec~n"
"\tT1/T2: ~.2f",
[NProcs,length(Modules),T1/1000000,T2/1000000,X]),
- if X < 1000 ->
- ct:fail({not_enough_improvement_after_purge,round(X)});
+ if X < 1 ->
+ ct:fail({no_improvement_after_purge,X});
true ->
ok
end;