Greg Stein wrote:
> Hey all,
>
> Just now, I was running the full test suite. While that was running
> the background, I started a commit from the libsvn_wc directory.
>
> Two problems:
>
> 1) subversion/... was locked. not just libsvn_wc
>
> 2) the test suite broke because it saw a lock down in tests/cmdline
>
>
> I think (1) is kind of normal; I'm not sure. The latter is
> problematic. It reported a lock on
> svn-test-work/working-copies/basic_tests-48. That should not have been
> there!
>
> I'm wondering if (somehow), the system is skip up from basic_tests-48/
> all the way to tests/cmdline. Seeing the depth=infinity lock there,
> and applying it to the test?
>
> It seems plausible, but also highly problematic :-(
>
> Anyone?
From time to time, I've seen evidence that our trunk code is walking up too
far in its parent tree as well, but every time I try to create a reliable
recipe, I can't. I have nothing but wc-1 working copies on my system for
day-to-day use. (I run subversion 1.6.x by default.) My home directory is
versioned, for example, as is the directory ~/tests (but nothing inside
~/tests is versioned). What I've seen, though, is that if I use trunk svn
to do some testing, creating working copies and such inside ~/test/,
sometimes I get errors that indicate that the client has crawled up out of
that wc-ng working copy and is looking at ~/test/. Obviously, it'd be fine
if it crawled up that far, realized that it had gone above the WC root, and
just gracefully realized that it had crawled too far. But instead, it fails
with an error. Unfortunately, I can't recall which error is presented:
"working copy is too old", perhaps.
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2010-03-11 15:47:55 CET