Re: On the stability of TAP tests for LDAP
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Date: 2019-07-24T09:01:47Z
Lists: pgsql-hackers
Attachments
- wait-for-slapd-v3.patch (application/octet-stream) patch v3
On Wed, Jul 24, 2019 at 7:50 PM Michael Paquier <michael@paquier.xyz> wrote: > Perhaps this worked on freebsd? Now that I test it, the test gets > stuck on my Debian box: > # waiting for slapd to accept requests... > # Running: ldapsearch -h localhost -p 49534 -s base -b > dc=example,dc=net -n 'objectclass=*' > SASL/DIGEST-MD5 authentication started > Please enter your password: > ldap_sasl_interactive_bind_s: Invalid credentials (49) > additional info: SASL(-13): user not found: no secret in > database Huh, yeah, I don't know why slapd requires credentials on Debian, when the version that ships with FreeBSD is OK with an anonymous connection. Rather than worrying about that, I just adjusted it to supply the credentials. It works on both for me. > pgperltidy complains about the patch indentation using perltidy > v20170521 (version mentioned in tools/pgindent/README). Fixed. -- Thomas Munro https://enterprisedb.com
Commits
-
Fix LDAP test instability.
- 77d5dea386f5 11.5 landed
- 3964d3bce9ca 12.0 landed
- 27cd521e6e70 13.0 landed