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

Win32 Tests -- locks-test

From: D.J. Heap <dj_at_shadyvale.net>
Date: 2005-04-02 01:04:32 CEST

I'm having trouble with Win32 tests on trunk -- locks-test.exe hangs
with the following call stack:

          ntdll.dll!_KiFastSystemCallRet@0
          ntdll.dll!_NtLockFile@40
          kernel32.dll!_LockFileEx@24
> libapr.dll!apr_file_lock
          locks-test.exe!svn_io_file_lock2
          locks-test.exe!svn_fs_fs__get_write_lock
          locks-test.exe!svn_fs_fs__commit
          locks-test.exe!svn_fs_fs__commit_txn
          locks-test.exe!svn_fs_commit_txn
          locks-test.exe!lock_credentials
          locks-test.exe!do_test_num
          locks-test.exe!main
          locks-test.exe!mainCRTStartup
          kernel32.dll!_BaseProcessStart@4

The tests ran fine about 2 weeks ago. It is blocking on LockFileEx
because the file (repos\write-lock) has already been locked once.

Can someone else confirm/deny this result on Win32? Is apr_file_lock's
'exclusive lock' behavior semantically different on Unixes or is this
test hanging on Linux also? I haven't deeply investigated yet, but will
try to this weekend. It seems like it could be caused by a previous
test function not cleaning everything, but that is just a guess.

DJ

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 2 01:07:36 2005

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