From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Noah Misch <noah@leadboat.com>
Cc: Petr Jelinek <petr.jelinek@2ndquadrant.com>
Cc: Erik Rijkers <er@xs4all.nl>
Cc: David Steele <david@pgmasters.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Craig Ringer <craig@2ndquadrant.com>
Cc: pgsql-hackers-owner@postgresql.org
Subject: Re: snapbuild woes
Date: Mon, 1 May 2017 18:10:04 -0400
Message-ID: <12f78f6b-3a18-2456-62f0-e2821213af1d@2ndquadrant.com> (raw)
In-Reply-To: <18057.1493658127@sss.pgh.pa.us>
References: <20170413045812.GA2917375@tornado.leadboat.com>
<20170417020404.GB2988768@tornado.leadboat.com>
<20170418041657.hvwss6hz73ghozp5@alap3.anarazel.de>
<20170420000906.75t6uo7bof5pazrq@alap3.anarazel.de>
<ad637c84-534d-b291-9b6c-458f1ff7f54b@2ndquadrant.com>
<20170422053458.z7kmzopqdyi2tai4@alap3.anarazel.de>
<20170429214201.GB799290@rfd.leadboat.com>
<4387.1493642807@sss.pgh.pa.us>
<20170501160918.j27fvngzuwspg7d6@alap3.anarazel.de>
<16845.1493656327@sss.pgh.pa.us>
<20170501164011.5xqwxwlpdoc6kc4o@alap3.anarazel.de>
<18057.1493658127@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 5/1/17 13:02, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
>> On 2017-05-01 12:32:07 -0400, Tom Lane wrote:
>>> But quite aside from the question of whether we can afford the cycles,
>>> it seems like the wrong approach. IMO the buildfarm is mainly for
>>> verifying portability, not for trying to prove that race-like
>>> conditions don't exist. In most situations we're going out of our way
>>> to ensure reproduceability of tests we add to the buildfarm sequence;
>>> but it seems like this is looking for irreproducible results.
>
>> Yea, I wondered about that upthread as well. But the tests are quite
>> useful nonetheless. Wonder about adding them simply as a separate
>> target.
>
> I have no objection to adding more tests as a non-default target.
Well, the problem with nondefault targets is that they are hard to find
if you don't know them, and then they will rot.
Sure, we need a way to distinguish different classes of tests, but lets
think about the bigger scheme, too. Ideas welcome.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, andres@anarazel.de, noah@leadboat.com, petr.jelinek@2ndquadrant.com, er@xs4all.nl, david@pgmasters.net, robertmhaas@gmail.com, craig@2ndquadrant.com, pgsql-hackers-owner@postgresql.org
Subject: Re: snapbuild woes
In-Reply-To: <12f78f6b-3a18-2456-62f0-e2821213af1d@2ndquadrant.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