Scott Schurr efe3700f70 Don't use JobQueue during shutdown (RIPD-1356): ...

If the JobQueue is used during shutdown then those Jobs may access
Stoppables after they have already stopped.  This violates the
preconditions of Stoppables and may lead to undefined behavior.

The solution taken here is to reference count all Jobs in the
JobQueue.  At stop time all Jobs already in the JobQueue are
allowed to run to completion, but no further Jobs are allowed
into the JobQueue.

If a Job is rejected from the JobQueue (because we are stopping),
then JobQueue::addJob() returns false, so the caller can make any
necessary adjustments.

2017-07-31 18:39:58 -04:00

..

Config_test.cpp

Add validator token to config (RIPD-1386)

2017-03-01 11:41:07 -05:00

Coroutine_test.cpp

Cleanup unit test support code (RIPD-1380):

2017-01-13 15:01:20 -08:00

CryptoPRNG_test.cpp

Add unit test for crypto_prng class

2017-03-31 14:53:44 -07:00

DeadlineTimer_test.cpp

Convert DeadlineTimer to chrono (RIPD-1189)

2016-12-23 14:36:10 -08:00

JobCounter_test.cpp

Don't use JobQueue during shutdown (RIPD-1356):

2017-07-31 18:39:58 -04:00

JobQueue_test.cpp

Don't use JobQueue during shutdown (RIPD-1356):

2017-07-31 18:39:58 -04:00

SociDB_test.cpp

Cleanup unit test support code (RIPD-1380):

2017-01-13 15:01:20 -08:00

Stoppable_test.cpp

Remove timing window from RootStoppable (RIPD-1392):

2017-03-20 17:49:16 -07:00

TerminateHandler_test.cpp

Remove beast::Thread (RIPD-1189):

2017-03-01 11:43:59 -05:00

Workers_test.cpp

Convert Workers to std::thread (RIPD-1189)

2017-01-13 15:01:20 -08:00