Re: On the stability of TAP tests for LDAP - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: On the stability of TAP tests for LDAP
Date
Msg-id CA+hUKGLheBpe2-Zw_PPUOsL+kKs10Fvne8kYS4DgAMowinJb-w@mail.gmail.com
Whole thread Raw
In response to Re: On the stability of TAP tests for LDAP  (Michael Paquier <michael@paquier.xyz>)
Responses Re: On the stability of TAP tests for LDAP  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
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

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: [bug fix] Produce a crash dump before main() on Windows
Next
From: Amit Kapila
Date:
Subject: Re: POC: Cleaning up orphaned files using undo logs