X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Yzay3UlJBm2rK80BmQzu8TNEZXWAn+Aw/yWsbViuWbm
	ME8whYwL06G7Vaz4EKmXwB9T+OY9s/9cO8951KxQJG4VAzIjkPgmBvVYRmyuvaQV
	nQSP2yYtSnM/Nkc0UIch8nqLHJHAVe6+fJveDyl25y/8XK55aOg84rKX/Ba7fScM
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=ez72LKLSnCjqbR2xfN12mcqCo10=; b=B5xaKj/U6c4ONLbLK
	nFXlx4W8FKfGqHjN3EMN89AVFxELALl7fCS5faxE+XqAzLvfE6t35yuyCXIWgirv
	krm877q+sq6I4WK7qepxlkrnOqN1ckdnApmNbEppXVudc0vAQob/j9v4AhU2+pJJ
	R9VDxjK3CAMlCD4Pu9EPLnj684=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1
Message-ID: <51AE06E7.7080005@acm.org>
Date: Tue, 04 Jun 2013 08:25:27 -0700
From: David Rothenberger <daveroth AT acm DOT org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
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> <20130604084128 DOT GB19572 AT calimero DOT vinschen DOT de> <20130604093749 DOT GA32667 AT calimero DOT vinschen DOT de>
In-Reply-To: <20130604093749.GA32667@calimero.vinschen.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 6/4/2013 2:37 AM, Corinna Vinschen wrote:
> On Jun  4 10:41, Corinna Vinschen wrote:
>> On Jun  3 17:58, David Rothenberger wrote:
>>> On 6/3/2013 1:11 PM, Warren Young wrote:
>>>> This is a big-push attempt at a version of Cygwin SQLite that will make
>>>> everyone happy (ha!) whether they want POSIX advisory locking behavior
>>>> or Windows mandatory locking behavior.  My part of the effort is being
>>>> stubborn on this point and doing the basic testing and packaging.  The
>>>> real magic was added by Corinna to yesterday's 1.7.19 cygwin1.dll snapshot.
>>> [...]
>>> ... 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.
>>
>> The question now is: Why?
> 
> IOW: It would be nice to have a simple testcase (plain C, only Cygwin
> POSIX calls, self-contained, yada yada) to see what sqlite expects in
> POSIX lock mode.

This may take some time or be completely over my head given all the
layers involved with the Subversion test suite (python bindings,
subversion code, libapr1). I probably won't get to it for a few days or
longer.

-- 
David Rothenberger  ----  daveroth AT acm DOT org

Kliban's First Law of Dining:
        Never eat anything bigger than your head.

--
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