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

Re: 'CVS-Unknown' buildfarm failures?

From: Jim Nasby <jnasby(at)pervasive(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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 14:42:03
Message-ID: B7CB5762-6EB5-470D-BECE-5013E7736588@pervasive.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Jun 2, 2006, at 10:27 AM, Andrew Dunstan wrote:
> Joshua D. Drake wrote:
>> Tom Lane wrote:
>>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>>> What's happening here is that cvs actually creates the directory  
>>>> and then later prunes it when it finds it is empty.
>>>
>>> I find that explanation pretty unconvincing.  Why would cvs print  
>>> a "?"
>>> for such a directory?
>>
>> cvs will print a ? if it doesn't know what it is... or is that svn?
>>
>
> 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.

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-06-03 14:56:44
Subject: Re: COPY (query) TO file
Previous:From: Greg StarkDate: 2006-06-03 14:22:19
Subject: Re: COPY (query) TO file

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