All the way back in
#2664302: Semaphore table is only used by a core service but it depends on system install →
we made the semaphore table optional. This did not account, however, for the table not existing in DatabaseLockBackend::releaseAll().
Because that method only does anything if a request that acquired a lock is being terminated, the use-case for hitting this is rather esoteric for regular sites, as it requires the following to happen in that exact order:
In functional tests, however, this is less esoteric to hit, if the last request of the functional test happens to have acquired a lock.
I have not been able to reproduce this locally, only on the Drupal.org CI. See https://git.drupalcode.org/project/config_overlay/-/jobs/6145015 for an example job in Config Overlay → . The actual error was hidden quite well, so I had to patch core to expose it in the job output.
Check for the semaphore table not existing in DatabaseLockBackend::releaseAll() and do nothing if it does not.
-
-
-
-
-
Active
11.0 🔥
lock system
Pipeline is green and here is the test-only job, which correctly fails on the missing table exception: https://git.drupalcode.org/issue/drupal-3540554/-/jobs/6158126