jfischoff
commented
2 years ago Sorry, this was a note to myself to update a test after a change was made to support the TMP environment variable (https://github.com/jfischoff/tmp-postgres/issues/256), I'm pretty sure. I don't think there was anything actually wrong.
The main issue that I've seen, that I have struggled to understand, is this one: https://github.com/jfischoff/tmp-postgres/issues/251.
The failure modes differ. Sometimes the failure occurs because the server refuses a connection, sometimes the connection times out, and sometimes an insert will fail because PostgreSQL complains that the database doesn't exist, despite our migration script having run and set up the database prior to the insert failing.
Huh this actually quite confusing.
Something to look out for is the postgres might not be shutting down correctly. This will result in it running out of semaphores when it starts. However typically, the error message will say this specifically.
dhess
Hi,
We've successfully deployed
tmp-postgresin our test suite now, and it's working great, except on our x86-64 Macs, where our tests will occasionally fail for strange reasons. If we re-run the failed job, it nearly always succeeds the second time.The failure modes differ. Sometimes the failure occurs because the server refuses a connection, sometimes the connection times out, and sometimes an insert will fail because PostgreSQL complains that the database doesn't exist, despite our migration script having run and set up the database prior to the insert failing.
For compatibility with Sqitch, which we're using for migrations, we run the server on
localhost:5423and connect via TCP loopback. We're making use oftmp-postgress database caching per your helpful blog post, though we're not yet using every trick in your arsenal, mainly just the initial approach you describe in that post. We also disable parallelism in our tests in order to achieve maximum isolation, and to keep the test harness relatively simple.We've yet to see any of these issues on our aarch64 Macs, nor our x86-64 Linux machines.
When I searched the tracker for "macos", I saw this issue. Can you provide some detail on what sorts of failures you're seeing? I'm curious if it has anything to do with our issues.