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
> 0x7FFFFFFFFFFFFFFF (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]
-----------------------------------------------------------------------------
