i've got an apparent RESOLUTION for some/most of the errors, & a
subsequent/new QUESTION ...
looking at the test code, the problem seems to be that,
::sqlite_opentemp_count 0
is never incremented from init val = 0.
that sure looks like temp file opening.
related, my current ./configure *is* with,
--enable-tempstore=yes
(
--enable-tempstore Use an in-ram database for temporary
tables
(never,no,yes,always)
)
changing that to,
--enable-tempstore=no
and re-config+building, then
./testfixture ../sqlite-3.3.8/test/conflict.test
finishes with NO errors.
Memory leaked: 0 bytes in 0 allocations
Thread-specific data deallocated properly
0 errors out of 127 tests
Failures on these tests:
checking also further,
./testfixture ../sqlite-3.3.8/test/lock2.test
(...)
0 errors out of 12 tests
(...)
./testfixture ../sqlite-3.3.8/test/malloc2.test
(...)
0 errors out of 18130 tests
(...)
./testfixture ../sqlite-3.3.8/test/lock2.test
(...)
0 errors out of 12 tests
(...)
./testfixture ../sqlite-3.3.8/test/pragma.test
(...)
0 errors out of 101 tests
(...)
which resolves most of the last 0.04% of test failures
so, QUESTION ... is this a problem with 'tempstore' setting in just
the TESTS, or does this indicate that tempstore should stay OUT of ram
in/for the app itself?
shouldn't the ::sqlite_opentemp_count increment on opening of RAM-based files?
but,
./testfixture ../sqlite-3.3.8/test/utf16.test
now reports,
(...)
9 errors out of 12034 tests
Failures on these tests: utf16-delete-8.1 utf16-delete-8.2
utf16-delete-8.3 utf16-delete-8.4 utf16-delete-8.5 utf16-delete-8.6
utf16-temptable-6.2 utf16-temptable-6.3 utf16-temptable-6.6
(...)
which are 'new' FAILS, where previously, the fail'd tests were,
utf16-conflict-6.2 utf16-conflict-6.3 utf16-conflict-6.7
utf16-conflict-6.8 utf16-conflict-6.9 utf16-conflict-6.10
utf16-conflict-6.11 utf16-conflict-6.12 utf16-conflict-6.13
utf16-lock2-1.1 utf16-lock2-1.3 utf16-lock2-1.4 utf16-lock2-1.6
utf16-lock2-1.7 utf16-lock2-1.10
i've traded in one set of errors for another with this one :-/
ideas?
thanks.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------