Re: Subversion 0.13.0 [Pre-Alpha] released - a report on successes and problems

Sorry if I'm boring the pants off everyone - tell me to stop when
necessary. Is any of this conversation of any help?

I tried the concurrent update example again, and it might be 'just' a
timing problem. The result the second time was:

$ svn up & sleep 1 && svn up

subversion/libsvn_wc/lock.c:47
svn_error: #21040 : <Attempted to lock an already-locked dir>
  working copy locked: ./subversion/tests/libsvn_delta

I'd regard that as a reasonable error message - in line with your
expectations, too.

The first instance of svn updated
subversion/tests/libsvn_delta/random-test.c,
subversion/libsvn_delta/compose_delta.c and packages/rpm/subversion.spec
(updated to revision 2288). These messages were interleaved with the
output above.

When I repeated the exercise again (no updates waiting), then both
completed without error - though there was some rattling on the disk drive.
The problem occurred on my system when there was some work to be done
fetching a new revision. That, of course, is a slow operation by
comparison with everything else that happens, so the first process is
delayed, allowing the second to catch it up. FWIW, when I did the first
troublesome run, there were no updates; I'd previously updated from r2263
to r2285, and there was no work to do for either 'svn up' on the concurrent
run.

--
Jonathan Leffler (jleffler@us.ibm.com)
STSM, Informix Database Engineering, IBM Data Management Solutions
4100 Bohannon Drive, Menlo Park, CA 94025
Tel: +1 650-926-6921   Tie-Line: 630-6921
      "I don't suffer from insanity; I enjoy every minute of it!"
                                                                                                                                       
                      Ben                                                                                                              
                      Collins-Sussman          To:       Jonathan Leffler/Menlo Park/IBM@IBMUS                                         
                      <sussman@collab.n        cc:       SVN Dev List <dev@subversion.tigris.org>, users@subversion.tigris.org         
                      et>                      Subject:  Re: Subversion 0.13.0 [Pre-Alpha] released - a report on successes and        
                      Sent by:                  problems                                                                               
                      sussman@collab.ne                                                                                                
                      t                                                                                                                
                                                                                                                                       
                                                                                                                                       
                      06/19/02 03:13 PM                                                                                                
                                                                                                                                       
                                                                                                                                       
"Jonathan Leffler" <jleffler@us.ibm.com> writes:
> Sorry about the way Lotus Notes handles embedded messages...
>
> Another question about 'svn up' - what prevents concurrent execution of
> 'svn up' on the same directory hierarchy?  I tried:
>
>       svn up & sleep 1 && svn up
>
> I didn't get an error about "already in use" (at least, not explicitly);
I
> got:
>
> subversion/libsvn_wc/adm_files.c:555
> apr_error: #17, src_err 0 : <File exists>
>   ./.svn/tmp/entries
That's odd.  Updates and commits *do* drop lockfiles into each .svn/
area, and do exactly what you're talking about below.
So I'm curious why that error isn't about an existing lockfile...
[...snippage...]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org