Re: pgsql: Test replay of regression tests, attempt II.

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Munro <tmunro(at)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Test replay of regression tests, attempt II.
Date: 2022-01-17 17:42:35
Message-ID: CA+hUKGKU=tiZoE7vp7qYFQNPdBd2pHoaOwkPMDg9YWk1h=FtmQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Jan 18, 2022 at 6:24 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
> > I'm quite appalled that this patch has apparently added an entire new run
> > of the core regression tests to the standard check-world/buildfarm cycle.

I wonder if there is a good way to share the resulting data directory
with the pg_upgrade test.

> These files should have been put into the tmp_check directory...
> that's what it's for.

Yeah, I mentioned this problem on the thread and was about to update
the clean target to remove them, but this sounds like a better idea.
Will fix.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-01-17 18:30:27 pgsql: Avoid calling strerror[_r] in PQcancel().
Previous Message Tom Lane 2022-01-17 17:24:48 Re: pgsql: Test replay of regression tests, attempt II.