pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christoph Berg <myon@debian.org>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: ldap tls test fails in some environments
Date: Thu, 14 May 2020 13:10:47 +0200
Message-ID: <20200514111047.GA445283@msg.df7cb.de> (raw)
In-Reply-To: <CA+hUKG+_n-zt1EAZaZfojjXh9StROu+880pRrXVvtQTWEC_UMg@mail.gmail.com>
References: <20200508191644.GA165095@msg.df7cb.de>
	<11682.1588966471@sss.pgh.pa.us>
	<20200508194533.GB165095@msg.df7cb.de>
	<20200513160544.GC373033@msg.df7cb.de>
	<CA+hUKG+_n-zt1EAZaZfojjXh9StROu+880pRrXVvtQTWEC_UMg@mail.gmail.com>

Re: Thomas Munro
> > 17:28:59 Data directory: /<<PKGBUILDDIR>>/build/src/test/ldap/tmp_check/t_001_auth_node_data/pgdata
> 
> I know nothing about Debian package building so I could be missing
> something about how this works, but I wonder if our script variable
> handling is hygienic enough for paths like that.

That's from the sbuild log filter, the special chars are not the
problem:

17:06:41 I: NOTICE: Log filtering will replace 'build/postgresql-13-fdfISX/postgresql-13-13~~devel~20200513.1505' with '<<PKGBUILDDIR>>'
17:06:41 I: NOTICE: Log filtering will replace 'build/postgresql-13-fdfISX' with '<<BUILDDIR>>'

> > It consistently fails on the build server, but works on my notebook.
> > Maybe that simply means slapd is crashing, but there's no slapd
> > output. Would it be possible to start slapd with "-d 255", even if
> > that means it doesn't background itself?
> 
> That'd require more scripting to put it in the background...

Maybe adding "&" is enough, provided it still writes the pid file for
shutting down...

> This leads me to suspect that something in your build server's
> environment that comes later in that list is overridding the
> TLS_REQCERT setting.  If that's the explanation, perhaps we should do
> this, which seems to work OK on my system, since it comes last in the
> list:

It's not messing with environment variables in that area.

I'll see if I can catch a shell in the environment where it fails.

Christoph





view thread (8+ messages)  latest in thread

Message-ID: <20200514111047.GA445283@msg.df7cb.de>
Permalink:  ../20200514111047.GA445283@msg.df7cb.de/
Also on:    postgresql.org/message-id/20200514111047.GA445283@msg.df7cb.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: myon@debian.org, thomas.munro@gmail.com
  Subject: Re: ldap tls test fails in some environments
  In-Reply-To: <20200514111047.GA445283@msg.df7cb.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox