On Fri, Jul 12, 2024 at 3:49 AM Dave Page <dp...@pgadmin.org> wrote: > So I received an off-list tip to checkout [1], a discussion around GSSAPI > causing test failures on windows that Alexander Lakhin was looking at. Thomas > Munro's v2 patch to try to address the issue brought me down to just a single > test failure with GSSAPI enabled on 17b2 (with a second, simple fix for the > OpenSSL/Kerberos/x509 issue): pg_dump/002_pg_dump. The relevant section from > the log looks like this:
I pushed that (ba9fcac7). > [15:28:42.692](0.006s) not ok 2 - connecting to a non-existent database: > matches > [15:28:42.693](0.001s) # Failed test 'connecting to a non-existent > database: matches' > # at C:/Users/dpage/git/postgresql/src/bin/pg_dump/t/002_pg_dump.pl line > 4689. > [15:28:42.694](0.001s) # 'pg_dump: error: connection to > server at "127.0.0.1", port 53834 failed: could not initiate GSSAPI security > context: No credentials were supplied, or the credentials were unavailable or > inaccessible: Credential cache is empty > # connection to server at "127.0.0.1", port 53834 failed: FATAL: database > "qqq" does not exist > # ' > # doesn't match '(?^:pg_dump: error: connection to server .* failed: > FATAL: database "qqq" does not exist)' Does it help if you revert 29992a6?
