IOT-2355: Change IPCA unit test agressive timeout.
authorSoemin Tjong <stjong@microsoft.com>
Wed, 24 May 2017 22:52:01 +0000 (15:52 -0700)
committerDan Mihai <Daniel.Mihai@microsoft.com>
Wed, 7 Jun 2017 18:13:31 +0000 (18:13 +0000)
commita4262755e4ad58ab669fc1f25ad1237582e14e94
treeb64ba2d4303b3a96afc549bfdd132006312c4d24
parented5038c9e5083a044f8928ddf0c26b59e13d1994
IOT-2355: Change IPCA unit test agressive timeout.

https://jira.iotivity.org/browse/IOT-2355

The IPCA unit test "IsIoTivityWorking" has failed sporadically.
This test directly uses IoTivity OC APIs to ensure that the underlying
IoTivity stack is working.
The 2 second timeout is incorrect, it should follow RFC 7252.

Change-Id: Iff640c2dbc2423e4865a4d2c8856a766d5345fa4
Signed-off-by: Soemin Tjong <stjong@microsoft.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/20375
Reviewed-by: Phil Coval <philippe.coval@osg.samsung.com>
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
resource/IPCA/unittests/ipcaunittests.cpp
resource/IPCA/unittests/testelevatorclient.cpp