Re: Add additional information to src/test/ssl/README - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Add additional information to src/test/ssl/README
Date
Msg-id 0C695367-70EF-4020-A1AA-A1034629FB76@yesql.se
Whole thread Raw
In response to Re: Add additional information to src/test/ssl/README  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Add additional information to src/test/ssl/README
List pgsql-hackers

> On 30 Oct 2021, at 20:12, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> I'd be inclined to add just one sentence to the boilerplate text these use,
> along the lines of

> "If the tests fail, examining the logs left behind in tmp_check/log/
> may be helpful."

Wouldn't it make more sense to start collecting troubleshooting advice in
src/test/perl/README and instead refer to that in the boilerplate?  I notice
that we don't document for example PG_TEST_NOCLEAN anywhere (which admittedly
is my fault), a trubleshooting section in that file would be a good fit.

--
Daniel Gustafsson        https://vmware.com/




pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.
Next
From: Justin Pryzby
Date:
Subject: Re: Vulnerability identified with Postgres 13.4 for Windows