This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Promote sqlite 3.7.13-1 from test status?
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Sat, 02 Mar 2013 08:53:18 +0100
- Subject: Re: Promote sqlite 3.7.13-1 from test status?
- References: <announce.5029275C.4040009@etr-usa.com> <502C0B7D.10909@etr-usa.com> <loom.20120816T092134-266@post.gmane.org> <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> <loom.20130301T155319-909@post.gmane.org> <5131312B.4000907@etr-usa.com>
Warren Young writes:
> I never have run the SQLite tests.
I see, thanks for letting me know. That adds another unknown in that
investigation, unfortunately.
> 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.
Yes, I guess that'd make sense.
>> the testsuite does
>> indeed produce a few of the dreaded disk I/O errors that seem to have
>> serious consequences.
>
> How?
The test result is different from the expected result, which might
indicate that the wrong data is returned (no overt database corruption
has happened, AFAICS). I haven't yet looked up what those tests are
actually trying to do.
> 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?
Since I can't know what to expect for the non-POSIX build (it might be
that these errors are triggered someplace else), I don't know if they
are a consequence of the (at the moment rather crude) changes I made.
Also, "disk I/O error" can unfortunately mean a lot of things, not just
locking, so even that is just an hypothesis at the moment. However,
"Windows programs" are always involved since I can't switch (completely)
off the virus scanner on the build machine.
> 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.
How do you know this wouldn't happen for the "normal Cygwin build? As I
said, while sqlite3 builds in this case, the testsuite doesn't. The
next step will be to try to use the testsuite from the POSIX build and
use it with the sqlite3 for Cygwin.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
--
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