[ET Trac] [Einstein Toolkit] #1395: GetComponents has trouble using svn in parallel at the Perimeter institute

[Einstein Toolkit]

#1395: GetComponents has trouble using svn in parallel at the Perimeter institute
----------------------------+-----------------------------------------------
  Reporter:  eschnett       |       Owner:  eric9              
      Type:  defect         |      Status:  review             
  Priority:  major          |   Milestone:                     
 Component:  GetComponents  |     Version:  development version
Resolution:                 |    Keywords:                     
----------------------------+-----------------------------------------------

Comment (by knarf):

 It could be that this problem is introduced because svn changed from .svn
 subdirs in every subdir of a checkout to a single .svn at the top of the
 checkout. When you request a checkout into a target directory, svn very
 likely checks if this isn't already a checkout. With the old system it
 only had to check for an existing .svn in that subdirectory. In our case
 there wasn't any. Now it has to 'go up', however, and might find one which
 at that time is 'in use', thus the error. If this is indeed how this was
 introduced, this is not very likely to go away in future versions.

 GetComponents has to be able to deal with that. We could either teach it
 that some versions of svn apparently have this problem, and disable
 parallel checkouts there (not my favorite, especially since this might
 mean all versions >=1.7), or we teach GetComponents that there are
 repositories that live 'within' other repositories and that the 'parents'
 have to be checked out first and completely before the 'children' can
 proceed. Right now the only such repo is the flesh.

 We could add a new keyword to CRL for this. One such possibility could be
 adding a !PRIORITY keyword to a section, specifying a number between 0 and
 100. Default would be not specified, and thus, 0. Nothing would change in
 the ET thornlist, except that for the flesh there would be an additional
 line
 {{{
 PRIORITY = 100
 }}}

 Only components with an identical number would be checked out in parallel.

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1395#comment:21>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit