Strange race-condition/possible bug in Subversion 1.7.0

Hi,

in the last weeks I developed a little Subversion tool. When I
heard about Subversion 1.7.0 I downloaded the source at the next
opportunity to run the functional tests against the new version.
With the new version two of the tests fail *sometimes*. The
tests use the command line and do about this:
                                             
    echo -n xxx >a
    svn add a
    svn commit -m 'c1' .

    svn copy a b
    echo -n yyy >b
    svn commit -m 'c2' .

Of cause I expect 'b' to contain 'yyy'. However sometimes it
contains 'xxx'. After this the repository is all consistent and fine
in my opinion (expect that 'a' has the unexpected content). However
the working copy looks strange. It behaves like that:

1) 'svn status' and 'svn diff' agree that there is no local change
   in 'b'.

2) If I just do a 'touch' on on 'b' without changing it's content,
   the svn command changes it's opinion. Now 'svn diff' and
   'svn status' agree that there is a local modification (xxx->yyy).

Since I added the equivalent of a 'sleep 1' just after the 'svn copy'
I have not seen the issue again.

Do you consider that a bug?
Is it already a known issue?

So far I have not subscribed to the list, so please answer also to
my personal address.

Regards
Harald Wilhelmi
Received on 2011-10-19 23:53:58 CEST