Skip site navigation (1) Skip section navigation (2)

Re: 'CVS-Unknown' buildfarm failures?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Jim Nasby <jnasby(at)pervasive(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, dpage(at)vale-housing(dot)co(dot)uk, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 'CVS-Unknown' buildfarm failures?
Date: 2006-06-03 16:30:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

Jim Nasby wrote:

>> yes, it's a file/directory it doesn't know about.
>> At one stage I suppressed these checks, but I found that too many  
>> times we saw errors due to unclean repos. So now buildfarm insists  
>> on having a clean repo.
>> I suppose I could provide a switch to turn it off ... in one recent  
>> case the repo was genuinely not clean, though, so I am not terribly  
>> keen on that approach - but I am open to persuasion.
> Another option would be to re-run cvs up one more time if we get any  
> unexpected files. It sounds like that would fix this issue on windows  
> machines, while still ensuring we had a clean repo to work from.

please see the new release of the buildfarm client, in which I have 
followed Tom's suggestion of removing the -P flag from the checkout and 
update commands - that should solve the Windows problem, as it will no 
longer try to remove the directory. I hope that solves the problem - if 
not I'll have a look at other solutions.



In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2006-06-03 16:36:40
Subject: Re: COPY (query) TO file
Previous:From: Greg StarkDate: 2006-06-03 15:45:52
Subject: Re: COPY (query) TO file

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group