tree 616d91a4d3b17efe31b1d9566e76caa13a6bf8f0
parent 010656b2ffba828db9179727087437e1e0701ed0
author Tobias Thierer <tobiast@google.com> 1498592933 +0100
committer Tobias Thierer <tobiast@google.com> 1498664105 +0100

Work around ServerSocketConcurrentCloseTest flakiness

The test involves 100 iterations of a client and server thread
connecting to each other and disconnecting over and over, until
the ServerSocket involved is closed at the end of the iteration.

Before this CL, each iteration took 50msec (counted from when
the threads signaled that they had started running by counting
down a latch. On recent builds on some devices, the two threads
didn't manage to establish any connection within those 50msec
but only when other tests had run previously. The exact cause
for this was not determined, but threads left over from over
from previous tests appeared to not be involved.

This CL increases the maximum time for each iteration to a maximum
of 150msec (in steps of 50msec, until at least one connection was
established), which makes the test pass (5/5 tries) on a device
where it previously consistently failed (15/16 tries failed).

Test: CtsLibcoreTestCases (on affected device)
Bug: 62859398

(cherry picked from commit 7956ee1980b5da2ede5d0555cabe5755fcaef813)

Change-Id: I19368fa2cac3b43f4c361b785c9ff3202c87652f