networksecurity/tls/ts_tls/scripts/tls_oom_wlan.ini
branchRCL_3
changeset 22 8d540f55e491
parent 21 abbed5a4b42a
child 23 425d8f4f7fa5
equal deleted inserted replaced
21:abbed5a4b42a 22:8d540f55e491
     1 // Copyright (c) 2010 Nokia Corporation and/or its subsidiary(-ies).
       
     2 // All rights reserved.
       
     3 // This component and the accompanying materials are made available
       
     4 // under the terms of "Eclipse Public License v1.0"
       
     5 // which accompanies this distribution, and is available
       
     6 // at the URL "http://www.eclipse.org/legal/epl-v10.html".
       
     7 //
       
     8 // Initial Contributors:
       
     9 // Nokia Corporation - initial contribution.
       
    10 //
       
    11 // Contributors:
       
    12 //
       
    13 // Description:
       
    14 /////////////////////////////////////////////
       
    15 
       
    16 #TLS Out of memory test
       
    17 
       
    18 /////////////////////////////////////////////
       
    19 [Tlstest]
       
    20 
       
    21 # READ ME!
       
    22 #
       
    23 ### This is the range of values for __UHEAP_FAILNEXT that are tested.
       
    24 ### TLS currently requires 846 heap allocations to make a connection.
       
    25 ### If the test has not passed by MaxFailureThreshold then it fails.
       
    26 ### This is to prevent the test running forever if the network or server is down.
       
    27 #
       
    28 # The above comment is outdated - in 8.0 it passes on the first iteration with 840.
       
    29 # The Comms Framework submission increases the threshold dramatically (as can be seen
       
    30 # below); this is at least substantially due to the new RFileLogger interface since
       
    31 # every single static logging call now makes an allocation (and the TLS client-side
       
    32 # has its own logging subsystem, hence a ten row hexdump becomes ten separate RFileLogger
       
    33 # calls).
       
    34 # Of course to be a strong OOM test the loop should start at one anyway, otherwise there
       
    35 # are many states we're not probing. It is suspected that the reason this is not done is two-
       
    36 # fold: firstly it would take a long time and so mightn't be suitable for routine run and
       
    37 # secondly and importantly the OpenSSL server currently used on the test network does not
       
    38 # handle spontaneous socket disconnection and so would need restarting after many of these
       
    39 # failures. Once a more robust test server is in place this part of the testing needs to be
       
    40 # revisited.
       
    41 
       
    42 FailureThreshold=1
       
    43 MaxThreshold=3200
       
    44 IPAddress=192.168.40.50
       
    45 IPPort=543