From: Noah Misch <noah@leadboat.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Move regression.diffs of pg_upgrade test suite
Date: Wed, 26 Dec 2018 14:44:28 -0800
Message-ID: <20181226224428.GA3277716@rfd.leadboat.com> (raw)
In-Reply-To: <22708.1545861757@sss.pgh.pa.us>
References: <20181224034411.GA3224776@rfd.leadboat.com>
<ede9f7a3-2082-ce59-abb0-fe867dc03bbb@2ndQuadrant.com>
<22708.1545861757@sss.pgh.pa.us>
On Wed, Dec 26, 2018 at 05:02:37PM -0500, Tom Lane wrote:
> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> > On 12/23/18 10:44 PM, Noah Misch wrote:
> >> A disadvantage of any change here is that it degrades buildfarm reports, which
> >> recover slowly as owners upgrade to a fixed buildfarm release. This will be
> >> similar to the introduction of --outputdir=output_iso. On non-upgraded
> >> animals, pg_upgradeCheck failures will omit regression.diffs.
> >>
> >> I think the right fix, attached, is to use "pg_regress --outputdir" to
> >> redirect these files to src/bin/pg_upgrade/tmp_check/regress.
>
> > Seems reasonable.
>
> Do we need to change anything in the buildfarm client to improve its
> response to this? If so, seems like it might be advisable to make a
> buildfarm release with the upgrade before committing the change.
> Sure, not all owners will update right away, but if they don't even
> have the option then we're not in a good place.
It would have been convenient if, for each test target, PostgreSQL code
decides the list of interesting log files and presents that list for the
buildfarm client to consume. It's probably overkill to redesign that now,
though. I also don't think it's of top importance to have unbroken access to
this regression.diffs, because defects that cause this run to fail will
eventually upset "install-check-C" and/or "check". Even so, it's fine to
patch the buildfarm client in advance of the postgresql.git change:
diff --git a/PGBuild/Modules/TestUpgrade.pm b/PGBuild/Modules/TestUpgrade.pmindex 19b48b3..dfff17f 100644--- a/PGBuild/Modules/TestUpgrade.pm+++ b/PGBuild/Modules/TestUpgrade.pm@@ -117,11 +117,16 @@ sub check
@checklog = run_log($cmd);
}
+ # Pre-2019 runs could create src/test/regress/regression.diffs. Its+ # inclusion is a harmless no-op for later runs; if another stage+ # (e.g. make_check()) failed and created that file, the run ends before+ # reaching this stage.
my @logfiles = glob(
"$self->{pgsql}/contrib/pg_upgrade/*.log
$self->{pgsql}/contrib/pg_upgrade/log/*
$self->{pgsql}/src/bin/pg_upgrade/*.log
$self->{pgsql}/src/bin/pg_upgrade/log/*
+ $self->{pgsql}/src/bin/pg_upgrade/tmp_check/*/*.diffs
$self->{pgsql}/src/test/regress/*.diffs"
);
foreach my $log (@logfiles)
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: noah@leadboat.com, tgl@sss.pgh.pa.us, andrew.dunstan@2ndquadrant.com
Subject: Re: Move regression.diffs of pg_upgrade test suite
In-Reply-To: <20181226224428.GA3277716@rfd.leadboat.com>
* 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