Subject: Re: [buildfarm-members] BuildFarm client release 4.19
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
 PostgreSQL-development <pgsql-hackers@postgresql.org>,
 buildfarm-members@postgresql.org
References: <3eef634f-4d0a-8f27-e4e9-67080b44f637@2ndQuadrant.com>
 <edb45e2b-b7b7-d817-fde8-e816f602025e@mksoft.nu>
 <f8c68fc8-7c95-c6d2-d759-9389982eda2f@2ndQuadrant.com>
 <1b1da59b-3280-7934-6a59-c57d8c86c84c@mksoft.nu>
 <ef6f298f-98de-aa0c-c898-8dbb985fb0af@mksoft.nu>
 <2cdca268-76ef-994f-5b87-ca37164fadf4@2ndQuadrant.com>
From: =?UTF-8?Q?Mikael_Kjellstr=c3=b6m?= <mikael.kjellstrom@mksoft.nu>
Message-ID: <dcabab00-8ecd-f0c5-d055-0f1f7598729a@mksoft.nu>
Date: Mon, 1 May 2017 21:00:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <2cdca268-76ef-994f-5b87-ca37164fadf4@2ndQuadrant.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


On 2017-05-01 20:56, Andrew Dunstan wrote:
> OK, coming up with a more comprehensive fix.

Ok.

> The obvious workaround for now is to create the directory and dont zap
> it or its parents. You should only have to do it once (per branch)

Yes, I know.  That is what I have been doing so far.  But if you want to 
rerun a branch from scratch it's much easier to just do:

rm -rf buildroot/HEAD
or
rm -rf buildroot/REL9_6_STABLE

and then the buildfarm script should do the right thing and create all 
the directories that it needs.

/Mikael


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