CRM-16387 - JobProcessMailingTest - Add comments about brokenness of mailerJobsMax...
authorTim Otten <totten@civicrm.org>
Mon, 15 Jun 2015 19:48:56 +0000 (12:48 -0700)
committerTim Otten <totten@civicrm.org>
Wed, 17 Jun 2015 23:30:04 +0000 (16:30 -0700)
commita2341a99e0c77d4ddcc7eeb9ccf69b461c8a0e3f
tree61a7d07f09c9696d2d98aa73481ba53bd25bb334
parentc1374ea133364816e7c6b80ac971dac6ff801138
CRM-16387 - JobProcessMailingTest - Add comments about brokenness of mailerJobsMax/lockHold

With the current MySQL-based lock-implementation, mailerJobsMax cannot be
enforced because the job locks (```data.mailing.job.*```) trample the worker
locks (```worker.mailing.*```).

The relevant tests are hacked (```lockHold```) so that they pass and loosely
approximate what *would* happen if the lock implementation were less
bonkers.
tests/phpunit/api/v3/JobProcessMailingTest.php