Erik Huelsmann wrote:
> Several weeks ago I asked CarlFK on IRC (#svn) to set up Win32 breakage
> tests on several other Windows flavors than the one sussman's system is
> running (W2k to be exact).
>
> He set up a machine testing on NTFS, which has been running its tests just
> fine, after initial startup problems. The other system (V400) has been
> running tests on FAT. This system has been failing the testsuite from the
> beginning and we haven't been able to fix it since. After a lot of fiddling
> with the system, I decided to verify testing on FAT with sussman's system.
>
> After switching sussman's testsystem to FAT, it started failing lots of
> tests. From the logs, I conclude that status incorrectly reports files as
> unchanged. Checking manually with TSVN, I see the same. 'touch'-ing the file
> turns it into a 'changed' status.
>
> What we have here is the problem that FAT has a 2 second timestamp
> resolution, whereas we only 'sleep-for-timestamps' for 1 second.
>
> Conclusion: We're currently broken for use on FAT.
>
> Question: What to do about it?
>
> Several possible answers:
> - Don't support FAT
> - Sleep an extra second for timestamps on Windows
> - Set timestamps to the last second which has already passed instead of the
> current one
> - (more?)
>
>
How does this effect use in the real world? My guess is the failure is due to the
automated test: update/sleep/check, which wouldn't happen in the real world.
Keep in mind I don't know why/what is sleeping, but... Could the time stamp check
adjust one side of the comparison by 2 or 4 seconds? This would cause a false
positive (i guess) which I also guess would cause un needed updates, but I bet it
would be A) very rare, and B) may be the only solution.
Carl K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 26 01:22:06 2005