[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: test failure on .36

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2004-01-23 00:48:48 CET

On Thu, 22 Jan 2004, Lee, Kevin wrote:

> This is on redhat 9.
> Since the problem was exhibited in both the file and http tests, I was assuming the problem was on the server side and not the client side.
> Is that possible?
> -----Original Message-----
> From: Branko Cibej [mailto:brane@xbc.nu]
> Sent: Thursday, January 22, 2004 3:27 PM
> To: Lee, Kevin
> Cc: dev@subversion.tigris.org; users@subversion.tigris.org
> Subject: Re: test failure on .36
> Lee, Kevin wrote:
> > This appears to be a problem due to running on a multiprocessor
> > machine. The errors are intermittent due to task scheduling. SVN
> > attempts to change a file to read-only, but the file does not exist
> > yet because a different thread (or process?) has not completed
> > creating the file yet.
> >
> I've been developing, running and testing SVN on a 2-cpu WinXP box for
> quite a while now, and haven't seen anything similar. Besides, the
> client and the tests run in a single thread; there can be no races there.
> (Note that there can be a race between the client and the server, and
> these show up on Windows in the test cleanup processing; we have code in
> the test suite that "fixes" that.)

I've been running on both RedHat 8 dual i686 and RedHat 9 dual AMD Athlon
processors for almost a year and have not encountered any problems.

David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 23 01:01:06 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.