X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_SV X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: Promote sqlite 3.7.13-1 from test status? Date: Mon, 11 Feb 2013 22:23:37 +0100 Lines: 41 Message-ID: <87halio886.fsf@Rainer.invalid> References: <502C0B7D DOT 10909 AT etr-usa DOT com> <20120816085016 DOT GB5536 AT calimero DOT vinschen DOT de> <502CCBB1 DOT 2070600 AT etr-usa DOT com> <20120816105507 DOT GD17546 AT calimero DOT vinschen DOT de> <502CE120 DOT 4050900 AT etr-usa DOT com> <20120816122654 DOT GG17546 AT calimero DOT vinschen DOT de> <502D1967 DOT 7090705 AT etr-usa DOT com> <20120816160656 DOT M21257 AT ds DOT net> <502D3A5C DOT 7010500 AT etr-usa DOT com> <00ad01cd7bf6$7cc68a50$76539ef0$@motionview3d.com> <1345169297 DOT 10004 DOT 10 DOT camel AT YAAKOV04> <87k3qmedzh DOT fsf AT Rainer DOT invalid> <51194F7F DOT 8050403 AT etr-usa DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.93 (gnu/linux) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi Warren, Warren Young writes: > From my perspective, though, I have a new problem, which is scraping > together enough free time to set up the SQLite test suite on a machine > here and set it to grinding, so I can exonerate the recent .15.1 > build. That's the second time I hear you talking about running the test suite for SQLite… where'd you get that from? > (This in response to David's report that the .15.1 builds cause > Cygwin svn to fail *its* test suite.) I've seen those particular tests grind to a halt or fail in my testing as well, with earlier versions of both subversion and sqlite. I'm not sure what is going on there, but it used to get better with newer versions of BerkeleyDB IIRC. > Until someone does that, even with a POSIX exponential backoff patch > in hand, I still can't move forward because I don't know if I'm just > trading one problem for another. As I said, it would be easier to effectively suppress the retry feature in the Windows-like build to see if the same error happens before making a foray into adding that feature to (POSIX && CYGWIN). > I'm also not entirely sure it's kosher for Cygwin SQLite to have > exponential lock retry backoffs when the Linux build doesn't. If Linux had a Win32 daemon that kept locking away files without telling it would probably need this as well. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- 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