It is more often that interesting information is buried by the verbose
output than the verbose output is useful. It can be reenabled later if
necessary.
Tests were failing with:
Error: Process completed with exit code 143.
This appears to mean that Github Actions killed the runner.
See https://github.com/jackc/pgx/actions/runs/8216337993/job/22470808811
for an example.
It appears Github Actions kills runners based on resource usage. Running
tests one at a time reduces the resource usage and avoids the problem.
Or at least that's what I presume is happening. It sure is fun debugging
issues on cloud systems where you have limited visibility... :(
fixes https://github.com/jackc/pgx/issues/1934
TLS setup and tests were rather finicky. It seems that openssl 3
encrypts certificates differently than older openssl and it does it in
a way Go and/or pgx ssl handling code can't handle. It appears that
this related to the use of a deprecated client certificate encryption
system.
This caused CI to be stuck on Ubuntu 20.04 and recently caused the
contributing guide to fail to work on MacOS.
Remove openssl from the test setup and replace it with a Go program
that generates the certificates.
Same issue as previous commit removing CockroachDB. numeric type only
supports infinity on PG 14 and there is no easy way in the current
test structure to skip tests based on server version.
pgtype has a ton of tests that don't work on CockroachDB. And because of
how the tests are structured it is difficult to skip just those tests.
pgtype may have significant changes before v5 is released so delay
updating these tests.