subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Corveleyn <jcor...@gmail.com>
Subject Re: Subversion Exception during cleanup
Date Fri, 18 May 2018 07:13:30 GMT
On Thu, May 17, 2018 at 11:28 PM, Eric Johnson <eric@tibco.com> wrote:
> On Thu, May 17, 2018 at 12:40 AM, Hartmut Leister <hardmooth@gmail.com>
> wrote:
>>
>> I encountered the following exceptions (see below) in the mid of
>> SVN-Cleanup.
>>
>> What I was doing:
>> - SVN-merge via TortoiseSVN, stopped with Error due to SVN-lock
>>   (small local changes separate from merged locations)
>> - SVN cleanup via TortoiseSVN on locked folder -> exception
>> - press [OK] -> next exception
>> - press [OK]
>> - trying cleanup again -> "Cleanup has successfully processed the
>> following paths: ..."
>>
>> Best wishes
>> Hartmut Leister
>>
>>
>> ---------------------------
>> Subversion Exception!
>> ---------------------------
>> Subversion encountered a serious problem.
>> Please take the time to report this on the Subversion mailing list
>> with as much information as possible about what
>> you were trying to do.
>> But please first search the mailing list archives for the error message
>> to avoid reporting the same problem repeatedly.
>> You can find the mailing list archives at
>> http://subversion.apache.org/mailing-lists.html
>>
>> Subversion reported the following
>> (you can copy the content of this dialog
>> to the clipboard using Ctrl-C):
>>
>> In file
>>
>> 'D:\Development\SVN\Releases\TortoiseSVN-1.9.4\ext\subversion\subversion\libsvn_client\cleanup.c'
>>  line 227: assertion failed (svn_dirent_is_absolute(dir_abspath))
>> ---------------------------
>> OK
>> ---------------------------
>>
>> followed by
>>
>> ---------------------------
>> TortoiseSVN
>> ---------------------------
>> Cleanup failed to process the following paths:
>> E:\Projekte\ORS_Applications\ORSOFT_7_5_1
>> sqlite[S5]: database is locked, executing statement 'PRAGMA
>>  case_sensitive_like=1;PRAGMA synchronous=OFF;PRAGMA
>>  recursive_triggers=ON;PRAGMA foreign_keys=OFF;PRAGMA locking_mode =
>>  NORMAL;PRAGMA journal_mode = TRUNCATE;'
>> Another process is blocking the working copy database, or the underlying
>> filesystem does not support file locking; if the working copy is on a
>> network filesystem, make sure file locking has been enabled on the file
>> server.
>> ---------------------------
>> OK
>> ---------------------------
>>
>>
>> Version info
>> TortoiseSVN 1.9.4, Build 27285 - 64 Bit , 2016/04/24 13:59:58
>> Subversion 1.9.4, -release
>> apr 1.5.2
>> apr-util 1.5.4
>> serf 1.3.8
>> OpenSSL 1.0.2g  1 Mar 2016
>> zlib 1.2.8
>> SQLite 3.12.1
>>
>> --
>>
>> Hartmut Leister <hardmooth@gmail.com>
>>
> Start with upgrading to a newer version of TortoiseSVN.
>
> Eric.
>

That's good advice in any case (latest 1.9 version is 1.9.7 I believe.
But 1.10.0 has also been released in the meantime).

OTOH, that particular error (libsvn_client/cleanup.c: line 227:
assertion failed (svn_dirent_is_absolute(dir_abspath))) seems to come
up once in a while, and I don't think it's root cause has been found
yet. I vaguely remember some previous discussions where it was hinted
that there might be a connection problem with the file storage (of the
working copy), or something else interfering. For example if the
working copy would be on a networked filesystem, and you lost
connection during the cleanup. I'm not sure though ...

@Hartmut: it would be very helpful if (1) you could reproduce this (if
possible with a scenario starting from scratch, so others can
reproduce it as well), and (2) what happens if you try it with 1.10.0.

-- 
Johan

Mime
View raw message