On Mon, May 18, 2026 at 08:41:45PM +0900, Michael Paquier wrote: > While reading through the module, I think that the LWLock > initialization logic is borked, where we decide to do a > LWLockInitialize() more times than necessary, confusing the internal > states. Honestly, I have no clue why the test has suddenly been > failing, and why other buildfarm members don't complain. The host has > been upgraded a couple of days ago to the latest Debian, but I also > had a few clean runs in the buildfarm before this began showing up. > What I do know is that the patch attached is able to make the tests of > the module pass for v16 on the problematic host with -DEXEC_BACKEND.
Hearing nothing, I have fixed that on REL_16_STABLE to bring back my animal to green. The tranche ID allocation calls are wasteful in the module for v17 and v18, but it does not really matter much for the sake of the tests. HEAD is in a much better state by saving the same names in shmem (pronounced as in "shmemme"). -- Michael
signature.asc
Description: PGP signature
