X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,TW_BD X-Spam-Check-By: sourceware.org Message-ID: <5131312B.4000907@etr-usa.com> Date: Fri, 01 Mar 2013 15:52:27 -0700 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Cygwin-L Subject: Re: Promote sqlite 3.7.13-1 from test status? References: <502C0B7D.10909@etr-usa.com> <20120816085016.GB5536@calimero.vinschen.de> <502CCBB1.2070600@etr-usa.com> <20120816105507.GD17546@calimero.vinschen.de> <502CE120.4050900@etr-usa.com> <20120816122654.GG17546@calimero.vinschen.de> <502D1967.7090705@etr-usa.com> <20120816160656.M21257@ds.net> <502D3A5C.7010500@etr-usa.com> <00ad01cd7bf6$7cc68a50$76539ef0$@motionview3d.com> <1345169297.10004.10.camel@YAAKOV04> <87k3qmedzh.fsf@Rainer.invalid> <51194F7F.8050403@etr-usa.com> <87halio886.fsf@Rainer.invalid> <511967DD.8030600@etr-usa.com> <87d2w6o6iq.fsf@Rainer.invalid> <5119E08B.6050909@etr-usa.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 3/1/2013 08:11, Achim Gratz wrote: > > how'd you work around the reams of errors in compiling the > testfixture (if you had to do anything)? I never have run the SQLite tests. The reason I brought it up is that it could possibly provide a counterargument against the "svn + bdb breaks" report. If SQLite's own extensive tests succeed, then we can be pretty sure the problem is BDB. I've been procrastinating on getting these tests running, which is why Cygwin SQLite remains at 3.7.13. At this point, I'm about to give up on it and ship an updated version of my latetst test packages. That is, with FTS and such features enabled, the Unix /tmp directory patch, and built in Windows mode. > the testsuite does > indeed produce a few of the dreaded disk I/O errors that seem to have > serious consequences. How? I mean, shouldn't the test suite be running only pure Cygwin programs, on files accessed only via cygwin1.dll, with POSIX locking only? If so, how can you run into locking errors? The reason this saga started with locking errors is that we were trying to mix POSIX and Windows native locking. That situation shouldn't continue within the SQLite test suite. -- 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