"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

• Re: 'CVS-Unknown' buildfarm failures? at 2006-06-04 13:18:59 from Andrew Dunstan

pgsql-hackers by date

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