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

Re: 'CVS-Unknown' buildfarm failures?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: 'CVS-Unknown' buildfarm failures?
Date: 2006-06-04 16:40:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
>>> 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.

> So what I'm going to try instead is a variation on Jim's suggestion above,
> but instead of re-running cvs update, what we'll do is a longish sleep (say
> 10 or 20 secs) which should be enough time for Windows to get its act
> together, and then run cvs status, which will also show us extraneous files.

Yeah, this is probably OK since you only need to do it if you see any ?
entries in the cvs update.  Another low-tech solution is to sleep a bit
and then see if any of the files/directories listed in ? entries are
still there.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2006-06-04 19:17:40
Subject: Re: 'CVS-Unknown' buildfarm failures?
Previous:From: Andrew DunstanDate: 2006-06-04 13:18:59
Subject: Re: 'CVS-Unknown' buildfarm failures?

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