Re: "make check" changes have caused buildfarm deterioration.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(dot)dunstan(at)pgexperts(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "make check" changes have caused buildfarm deterioration.
Date: 2015-07-21 10:52:20
Message-ID: 20150721105220.GC5596@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund wrote:
> On 2015-07-21 14:39:42 +0900, Michael Paquier wrote:
> > Regarding initdb.log and postmaster.log, this is definitely a bug.
> > Those have been moved by dcae5fa from log/ to tmp_check/log/,
> > tmp_check/ getting removed at the end of pg_regress if there are no
> > failures counted.
>
> FWIW, I think that's bad TM. Especially when comparing good/bad
> buildfarm runs the ability to get logs from good runs is essential.

Hm, okay, so let's put it back where it was.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2015-07-21 11:00:31 Re: Fillfactor for GIN indexes
Previous Message Andres Freund 2015-07-21 10:18:44 Re: RFC: replace pg_stat_activity.waiting with something more descriptive