RE: Corrupt files when quickly committing...

This could also be dependent upon the design of the process that's
outputting the 100 files. What kind of process is this?

You could easily check if the TSVN cache process is interfering by killing
the cache process and re-running your script. The TSVN cache process
shouldn't restart unless you view the contents of your hard drive through
explorer during the script run.

-----Original Message-----
From: Tankko [mailto:tankko@gmail.com]
Sent: Thursday, June 29, 2006 6:39 PM
To: users@tortoisesvn.tigris.org
Subject: Corrupt files when quickly committing...

I am running into a strange problem:

I am running on WinXP, with the latest versions of svn and TSVN.

I have a program that runs and creates about 100 files in the 100K range and
dumps them into a directory that is under version control.
The 100 files already exist and most will not have changed, but some do.

It takes about 2 seconds for the program to write out these 100 files.

The next step in my batch file is to so a "svn commit" using the command
line tool. Everything looks OK, the files that have changed are sent to the
repository with no errors.

Problems is, 1 to 5 files are corrupt.

If I don't do the "svn commit" step in the batch file and wait 10 or 20
seconds, then do the svn commit, everything is fine.

The program that creates these files isn't complaining about any files that
it can't open, close or write to.

Is this the TSVN background process messing something up?

Tankko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Jun 30 00:52:06 2006