From: Andrew Dunstan <andrew@dunslane.net>
Subject: buildfarm client release 4.18
To: PostgreSQL-development <pgsql-hackers@postgresql.org>,
 buildfarm-members@postgresql.org
Message-ID: <d42f4f4f-8f0e-6e9d-0af2-e13d4ca1cc74@dunslane.net>
Date: Tue, 11 Oct 2016 20:24:34 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


I have just released buildfarm client version 4.18.


In addition to some minor fixes, there are two significant changes:


  * The client now makes a determined effort to clean up any left over
    build artefacts from previous runs at the start of a run. It also
    tries to clean away old socket files. That means that manual fixes
    are much less likely to be required, if the script has crashed or
    the machine has crashed or restarted.
  * There is a new config parameter "wait_timeout", which defaults to
    undefined. If it is set then any run that takes longer than the
    specified number of seconds is aborted. That means that runs that
    get stuck will time out, and the whole animal won't be stuck and
    requiring manual intervention. My test animal has a setting of 3 *
    3600, i.e. 3 hours. There is some possible danger in this, that we
    might miss bugs that cause us to get stuck, so at least some animals
    should not use this feature.


The release can be downloaded from: 
<http://www.pgbuildfarm.org/downloads/releases/build-farm-4_18.tgz>


cheers


andrew


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers