Re: Add additional information to src/test/ssl/README

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Burke <kevin(at)burke(dot)dev>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add additional information to src/test/ssl/README
Date: 2021-10-30 18:41:45
Message-ID: 0C695367-70EF-4020-A1AA-A1034629FB76@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 30 Oct 2021, at 20:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-10-30 19:10:32 Re: Vulnerability identified with Postgres 13.4 for Windows
Previous Message Jeff Davis 2021-10-30 18:14:35 Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.