This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [TEST] sqlite3-3.7.17-1 (Cygwin 1.7.19 locking feature)
- From: David Stacey <drstacey at tiscali dot co dot uk>
- To: cygwin at cygwin dot com
- Date: Tue, 04 Jun 2013 17:22:53 +0100
- Subject: Re: [TEST] sqlite3-3.7.17-1 (Cygwin 1.7.19 locking feature)
- References: <51ACF886 dot 10301 at etr-usa dot com> <51AD3BB4 dot 2010601 at acm dot org>
On 04/06/13 01:58, David Rothenberger wrote:
... initial results with the Subversion test suite (for 1.8.0-rc2) show
that most tests fail with a "sqlite: database is locked (S5)" error
unless CYGWIN_SQLITE_LOCKING=posix.
It appears that much water has already passed under the proverbial
bridge, but I gave this a test and also suffered from the same problems.
Environment was WinXP SP3 with Cygwin snapshot 2013-06-03 and
TortoiseSVN 1.7.13. I found that a reverse merge crashed quite reliably:
$ svn merge -r 5606:5605 file.txt
svn: E200033: database is locked, executing statement 'RELEASE s0'
$ export CYGWIN_SQLITE_LOCKING=posix
$ svn merge -r 5606:5605 file.txt
svn: E200030: disk I/O error, executing statement 'RELEASE s12'
svn: E200030: sqlite: disk I/O error
svn: E200030: sqlite: disk I/O error
svn: E200030: no such savepoint: s13, executing statement 'RELEASE s13'
svn: E200030: no such savepoint: s13, executing statement 'ROLLBACK TO s13'
Cheers,
Dave.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple