On 14.06.2018 18:09, Philip Martin wrote: > Philip Martin <phi...@codematters.co.uk> writes: > >> Julian Foad <julianf...@apache.org> writes: >> >>> The most unusual thing about these failing tests is the data they >>> write. Strings of 5 or 6 low-value bytes, like: >>> >>> '\0\1\2\3\4\5' >>> '\5\4\3\2\1\0' >> Those are the same size. Could it be a filesystem timestamp resolution >> issue? The file changes but the timestamp does not and some change is >> not detected? > An HFS+ filesystem has a coarse 1s timestamp resolution so that would > explain why the problem shows up there but not systems with subsecond > resolution. > > Neither shelve or unshelve appear to use svn_sleep_for_timestamp().
Oh, bravo! This could indeed be the problem. -- Brane
