Re: [sqlite] test failures on cygwin
On Saturday 22 September 2007 14:20, Evans, Mark (Tandem) wrote: > It's hard to drag my Linux server to Starbucks. :-) > > Next Windows laptop, though, will definitely have to have a > Linux/Windows dual personality. I'll have to wait until the next > mega-merger for a Mac. > > Mark > If your HD has the space load Suse Linux from Novel and run Windos or Linux. You can down load for free Novel's latest version. jim-on-linux http://www.inqvista.com > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Friday, September 21, 2007 6:05 PM > > To: sqlite-users@sqlite.org > > Subject: Re: [sqlite] test failures on cygwin > > > > > Of course, the easiest option by far is to use a Linux box or > > a Mac. :-) > > > > -- > > D. Richard Hipp <[EMAIL PROTECTED]> > > --- >-- To unsubscribe, send email to > [EMAIL PROTECTED] > --- >-- - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] test failures on cygwin
It's hard to drag my Linux server to Starbucks. :-) Next Windows laptop, though, will definitely have to have a Linux/Windows dual personality. I'll have to wait until the next mega-merger for a Mac. Mark > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, September 21, 2007 6:05 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] test failures on cygwin > > > Of course, the easiest option by far is to use a Linux box or > a Mac. :-) > > -- > D. Richard Hipp <[EMAIL PROTECTED]> > - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] test failures on cygwin
Evans, Mark (Tandem) wrote: So it looks like I have a cygwin TCL issue. Is this fixable? You can load Active State Tcl and use that instead of the version that comes with Cygwin. You get lots of extra goodies, in addition to an up-to-date Tcl core. HTH, Gerry - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] test failures on cygwin
"Evans, Mark (Tandem)" <[EMAIL PROTECTED]> wrote: > ** > N.B.: The version of TCL that you used to build this test harness > is defective in that it does not support 64-bit integers. Some or > all of the test failures above might be a result from this defect > in your TCL build. > ** Yeah. That's what I figured. You need to fix you TCL build. It's *still* not to late to switch to Linux or Mac :-) -- D. Richard Hipp <[EMAIL PROTECTED]> - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] test failures on cygwin
"Evans, Mark (Tandem)" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have been lurking on the message board and am in awe of the collective
> wisdom.
>
> I'm just getting my feet wet learning the internals of SQLite, drinking
> from the proverbial firehose. I am using cygwin 1.90 as my learning
> platform and I have built SQLite 3.5.0. I ran 'make test' (quick.test
> suite) and it reports some test failures as follows:
>
> 41 errors out of 28604 tests
> Failures on these tests: autoinc-6.1 bind-3.1 cast-3.1 cast-3.2 cast-3.4
> cast-3.5 cast-3.6 cast-3.8 cast-3.11 cast-3.12 cast-3.14 cast-3.15
> cast-3.16 cast-3.18 cast-3.21 cast-3.22 cast-3.24 expr-1.102 expr-1.106
> func-18.14 func-18.16 func-18.17 func-18.31 lastinsert-8.1
> lastinsert-9.1 misc1-9.1 misc2-4.1 misc2-4.2 misc2-4.4 misc2-4.5
> misc2-4.6 misc3-3.6 misc3-3.7 misc3-3.8 misc3-3.9 misc3-3.10 misc3-3.11
> misc5-2.2 shared-1.11.9 shared-2.11.9 types-2.1.8
>
> Should I be surprised by these failures?
>
> Taking the first one that failed, autoinc-6.1, it reported:
>
> autoinc-6.1...
> Expected: [9223372036854775807]
> Got: [-1]
>
> The corresonding test code is:
>
> ifcapable {!rowid32} {
> do_test autoinc-6.1 {
> execsql {
> CREATE TABLE t6(v INTEGER PRIMARY KEY AUTOINCREMENT, w);
> INSERT INTO t6 VALUES(9223372036854775807,1);
> SELECT seq FROM main.sqlite_sequence WHERE name='t6';
> }
> } 9223372036854775807
> }
>
> So the SELECT clause returns -1 instead of the expected
> 0x7FFF (MAXLONGLONG), or in other words MAXLONGLONG + 1.
> Should the value returned by SELECT seq ... be the the key value (rowid)
> of the last insert, or, is seq supposed to represent the next rowid
> (autoincrement of last key)?
>
41 failures out of 28604 isn't bad. That's a 0.1% failure rate. If
these are the only problems you are having, your build is probably OK.
If you want to go for 100% pass, the first place I would look is what
version of TCL you are linking against to build the test harness.
You want a later version of 8.4 or any version of 8.5. I'll bet you
have 8.3, which won't work here.
The other thing you might try to do is *not* use cygwin but instead
use mingw.
Of course, the easiest option by far is to use a Linux box or a Mac. :-)
--
D. Richard Hipp <[EMAIL PROTECTED]>
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
RE: [sqlite] test failures on cygwin
When I run just autoinc.test alone, I get the following summary
output:
54 errors out of 66 tests
Failures on these tests: autoinc-6.1 autoinc-1.1 autoinc-1.2 autoinc-1.3
autoinc-1.4 autoinc-1.6 autoinc-2.1 autoinc-2.2 autoinc-2.3 autoinc-2.4
autoinc-2.5 autoinc-2.6 autoinc-2.7 autoinc-2.8 autoinc-2.9 autoinc-2.10
autoinc-2.11 autoinc-2.12 autoinc-2.13 autoinc-2.21 autoinc-2.23
autoinc-2.25 autoinc-2.27 autoinc-2.29 autoinc-2.51 autoinc-2.52
autoinc-2.53 autoinc-2.54 autoinc-2.55 autoinc-2.70 autoinc-2.71
autoinc-2.72 autoinc-2.73 autoinc-2.74 autoinc-3.1 autoinc-3.2
autoinc-3.3 autoinc-3.4 autoinc-4.1 autoinc-4.2 autoinc-4.3 autoinc-4.4
autoinc-4.4.1 autoinc-4.5 autoinc-4.6 autoinc-4.7 autoinc-4.8
autoinc-4.9 autoinc-4.10 autoinc-5.1 autoinc-5.2 autoinc-5.3 autoinc-5.4
autoinc-7.1
**
N.B.: The version of TCL that you used to build this test harness
is defective in that it does not support 64-bit integers. Some or
all of the test failures above might be a result from this defect
in your TCL build.
**
All memory allocations freed - no leaks
Maximum memory usage: 76060 bytes
So it looks like I have a cygwin TCL issue. Is this fixable?
Mark
> -Original Message-
> From: Evans, Mark (Tandem)
> Sent: Friday, September 21, 2007 5:47 PM
> To: sqlite-users@sqlite.org
> Subject: [sqlite] test failures on cygwin
>
> Hi all,
>
> I have been lurking on the message board and am in awe of the
> collective wisdom.
>
> I'm just getting my feet wet learning the internals of
> SQLite, drinking from the proverbial firehose. I am using
> cygwin 1.90 as my learning
> platform and I have built SQLite 3.5.0. I ran 'make test'
> (quick.test
> suite) and it reports some test failures as follows:
>
> 41 errors out of 28604 tests
> Failures on these tests: autoinc-6.1 bind-3.1 cast-3.1
> cast-3.2 cast-3.4
> cast-3.5 cast-3.6 cast-3.8 cast-3.11 cast-3.12 cast-3.14 cast-3.15
> cast-3.16 cast-3.18 cast-3.21 cast-3.22 cast-3.24 expr-1.102
> expr-1.106
> func-18.14 func-18.16 func-18.17 func-18.31 lastinsert-8.1
> lastinsert-9.1 misc1-9.1 misc2-4.1 misc2-4.2 misc2-4.4 misc2-4.5
> misc2-4.6 misc3-3.6 misc3-3.7 misc3-3.8 misc3-3.9 misc3-3.10
> misc3-3.11
> misc5-2.2 shared-1.11.9 shared-2.11.9 types-2.1.8
>
> Should I be surprised by these failures?
>
> Taking the first one that failed, autoinc-6.1, it reported:
>
> autoinc-6.1...
> Expected: [9223372036854775807]
> Got: [-1]
>
> The corresonding test code is:
>
> ifcapable {!rowid32} {
> do_test autoinc-6.1 {
> execsql {
> CREATE TABLE t6(v INTEGER PRIMARY KEY AUTOINCREMENT, w);
> INSERT INTO t6 VALUES(9223372036854775807,1);
> SELECT seq FROM main.sqlite_sequence WHERE name='t6';
> }
> } 9223372036854775807
> }
>
> So the SELECT clause returns -1 instead of the expected
> 0x7FFF (MAXLONGLONG), or in other words MAXLONGLONG + 1.
> Should the value returned by SELECT seq ... be the the key
> value (rowid) of the last insert, or, is seq supposed to
> represent the next rowid (autoincrement of last key)?
>
> Regards,
> Mark
>
>
> --
> ---
> To unsubscribe, send email to [EMAIL PROTECTED]
> --
> ---
>
>
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
