Re: Buildfarm client version 4.15 released

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PGBuildFarm <pgbuildfarm-members(at)pgfoundry(dot)org>
Subject: Re: Buildfarm client version 4.15 released
Date: 2015-04-18 15:01:08
Message-ID: 553271B4.6040604@dunslane.net
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: buildfarm-members pgsql-hackers


Unfortunately, this release contained a bug that only affects MSVC
builds, which would silently fail on HEAD.

There is a bug fix release available at
<http://www.pgbuildfarm.org/downloads/releases/build-farm-4_15_1.tgz> or
you can just pick up the fixed version of run_build.pl (the only thing
changed) at
<https://raw.githubusercontent.com/PGBuildFarm/client-code/b80efc68c35ef8a1ced37b57b3d19a98b8ae5dd2/run_build.pl>

Sorry for the inconvenience.

cheers

andrew

On 04/17/2015 10:33 AM, Andrew Dunstan wrote:
> I have just released version 4.15 of the PostgreSQL Buildfarm Client
> <http://www.pgbuildfarm.org/downloads/releases/build-farm-4_15.tgz>.
> It can be downloaded at
> <http://www.pgbuildfarm.org/downloads/releases/build-farm-4_15.tgz>
>
> Here's what's changed:
>
> * support the new location for pg_upgrade
> * support running tests of client programs
> * support building, installing and running testmodules
> * use a default ccache directory
> * improve logging when running pg_upgrade tests
> * handle odd location of Python3 regression tests
> * add timestamp to default log_line_prefix
> * make qw() errors in the config file fatal (helps detect errors)
> * minor bug fixes for web script settings.
> * allow for using linked git directories in non-master branches
>
> The last item might need a little explanation. Essentially this can
> reduce quite dramatically the amount of space required if you are
> building on more than one branch. Instead of keeping, say, 6 checked
> out repos for the current six tested branches, we keep one and link
> all the others to it. This works almost exactly the way
> git-new-workdir does (I stole the logic from there). This doesn't work
> in a couple of situations: if you are using Windows or if you are
> using git-reference. In these cases the new setting is simply ignored.
>
> To enable this new setting in an existing installation, do the
> following after installing the new release:
>
> * in your config file, add this setting:
> git_use_workdirs => 1,
> * remove the pgsql directory in each branch directory other than HEAD
>
> Another good thing to do in existing installations would be to add
> "%m" to the beginning of the log_line_prefix setting in extra_config
> stanza.
>
> Enjoy!
>
> cheers
>
> andrew
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2015-04-18 18:35:29 Re: mogrify and indent features for jsonb
Previous Message Michael Paquier 2015-04-18 11:38:44 Re: TABLESAMPLE patch

Browse buildfarm-members by date

  From Date Subject
Next Message Tom Lane 2015-05-16 00:31:56 [Pgbuildfarm-members] A few PG buildfarm members need to be restarted(?)
Previous Message Andrew Dunstan 2015-04-17 14:33:04 Buildfarm client version 4.15 released