Re: TAP backpatching policy

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TAP backpatching policy
Date: 2017-05-31 18:36:16
Message-ID: 20170531183615.GQ3151@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom, Alvaro,

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > My main concern is how widely is the buildfarm going to test the new
> > test frameworks. If we backpatch PostgresNode-based tests to 9.2, are
> > buildfarm animals going to need to be reconfigured to use
> > --enable-tap-tests?
>
> Yes. The animals that are doing it at all are using code more or less
> like this:
>
> if ($branch eq 'HEAD' or $branch ge 'REL9_4')
> {
> push(@{$conf{config_opts}},"--enable-tap-tests");
> }
>
> (verbatim from longfin's config script)
>
> So maybe that's an argument for not going back before 9.4. OTOH,
> you may be giving the buildfarm owners too little credit for
> willingness to update their configurations.

I'm certainly on the optomistic side of the equation here when it comes
to buildfarm owners. Generally speaking, I've seen them be pretty
reasonably responsive when asked to make a change or update something,
and a lot of them are also regular PG contributors, but even those who
aren't seem to take the buildfarm seriously and I expect an email going
out to them would certainly have a majority positive response.

Thanks!

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-05-31 18:39:31 Re: Re: [GENERAL] pg_basebackup error: replication slot "pg_basebackup_2194" already exists
Previous Message Stephen Frost 2017-05-31 18:33:12 Re: TAP backpatching policy