Currently ExternalRecordStoreTest::NamedPipeMultiplePipes4 test case is creating 100 threads and looking at various test agent logs and core dump stack traces at the time of timeout error, it looks like 100 threads is too much for some of small test machines. If writer threads can't be created, named pipes can't be created and the test thread waits for all writer threads to be created, which can't be satisfied due to thread resource limit. It's a self deadlock situation.

Reduce the number of threads for the test case. Reducing the number of threads makes sense, considering the test suite is unit test which should not require too much resources.