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

Re: Neon test failures explained.

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Fri, 15 May 2009 14:32:33 -0400

Now, a follow-up. Unless I'm mistaken, something about the new codebase
seems to be causing no wcprops to be stored in the working copy. *That's* a
bug in the new wcprop logic, and one that needs to be fixed.

Fortunately, it seems (in IRC) that at least Hyrum already knew about this

C. Michael Pilato wrote:
> I think I've *finally* determined that the remaining Neon test failures are,
> once again, related to wcprops. But this time, it's not the new wcprops
> code that really takes the blame here.
> Here's a simple test script (which expects that ~/.subversion/servers
> demands Neon):
> ------------------------------------------------------------------------
> #!/bin/sh
> set -x
> rm -rf repos wc
> svnadmin create repos
> svn co http://localhost/tests/repos wc
> (cd wc; make-greek-tree .)
> svn ci -m "" wc
> svn up wc
> svn pset foo bar wc
> svn ci -m "" wc
> svn up -r1 wc
> svn pset foo eek wc
> ### Uncomment this line to see Total Failure
> #find wc -name all-wcprops | xargs rm
> echo "### The following commit should fail do to out-of-dateness. ###"
> svn ci -m "" wc
> ------------------------------------------------------------------------
> As-is, the test does what is expected. But if you uncomment the line that
> purges the wcprops from the working copy, the final commit does not detect
> its out-of-dateness. This is a bug in Neon, period. The DAV RA layers are
> expected to be resilient in the face of a missing DAV cache, which only
> exists for performance reasons.

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2009-05-15 20:33:19 CEST

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