Re: build farm failures - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: build farm failures
Date
Msg-id 46C43525.1000105@dunslane.net
Whole thread Raw
In response to build farm failures  (Michael Meskes <meskes@postgresql.org>)
Responses Re: build farm failures  (Darcy Buskermolen <darcy@ok-connect.com>)
List pgsql-hackers

Michael Meskes wrote:
> Hi,
>
> we have two build farm members failing to make since I committed teh
> ecpg changes: echidna and herring.
>
> It looks like they are still using an old preproc.c although they
> checked out the new preproc.y. I have no idea how this is supposed to
> work so could someone please enlighten me?
>
>   

Yes it looks like that. But the buildfarm client doesn't actually build 
in the repo normally - it builds in a temp copy which is removed at the 
end of the run, precisely to avoid this kind of problem, so I'm a bit 
mystified how it can happen. In fact we go to some lengths to ensure 
that there are no extraneous files, but this one might not get caught by 
that because it is is in .cvsignore. This sort of thing is usually a 
symptom of somebody having run a build in the repo directly, a thing 
that buildfarm owners have been repeatedly advised not to do.

Anyway, the simple solution is to ask Darcy to blow away the repo (these 
buildfarm clients share a single cvs checkout) so that the buildfarm 
client will get a fresh checkout next time it's run.

cheers

andrew


pgsql-hackers by date:

Previous
From: Michael Paesold
Date:
Subject: Re: tsearch2 in PostgreSQL 8.3?
Next
From: "Simon Riggs"
Date:
Subject: Re: XID wraparound and busy databases