I've run the test several times on a G5 PowerMac and I have never seen the problem. I know at least some of the official Mac OS X testing for sqlite is done on a G5. That may explain why this hasn't been seen a lot by the development team.
I've enclosed the results of two test runs from today's cvs sources checked out into a new empty directory on my PowerBook G4. A similar run on a G5 PowerMac succeeded. In all cases, this is Mac OS X 10.3.8 with all current updates.
The intermittent nature of the failure suggests to me that it is some kind of timing-related problem. I'll be happy to work with anyone to try to debug this or test possible fixes.
--Steve
========================
Run 1:
========================
% make test > 045111010405.log 2>& 1
% grep -v Ok 045111010405.log
[... build steps omitted...]
creating sqlite3
./testfixture ../sqlite/test/quick.test
attach-5.2...
Expected: [0 {}]
Got: [1 {database is locked}]
attach-5.3...
Expected: [1 {trigger r5 cannot reference objects in database orig}]
Got: [1 {no such trigger: r5}]
attach-5.4...
Expected: [1 {trigger r5 cannot reference objects in database temp}]
Got: [1 {no such table: main.t5}]
attach-5.5...
Expected: [1 {trigger r5 cannot reference objects in database temp}]
Got: [1 {no such table: main.t5}]
attach-5.6...
Expected: [1 {trigger r5 cannot reference objects in database temp}]
Got: [1 {no such table: main.t5}]
attach-5.7...
Expected: [1 {trigger r5 cannot reference objects in database temp}]
Got: [1 {no such table: main.t5}]
attach-5.7...
Expected: [1 {trigger r5 cannot reference objects in database temp}]
Got: [1 {no such table: main.t5}]
attach-5.8...
Expected: [1 {trigger r5 cannot reference objects in database temp}]
Got: [1 {no such table: main.t5}]
attach-5.9...
Expected: [1 {trigger r5 cannot reference objects in database temp}]
Got: [1 {no such table: main.t5}]
autovacuum-ioerr-5.38.3...
Expected: [1]
Got: [0]
autovacuum-ioerr2-4.132.3...
Expected: [1]
Got: [0]
time with cache: 2097973 microseconds per iteration
time without cache: 4028552 microseconds per iteration
11 errors out of 19709 tests
Failures on these tests: attach-5.2 attach-5.3 attach-5.4 attach-5.5 attach-5.6 attach-5.7 attach-5.7 attach-5.8 attach-5.9 autovacuum-ioerr-5.38.3 autovacuum-ioerr2-4.132.3
make: *** [test] Error 1
======================== Run 2: ========================
% make test > 594512010405.log 2>& 1 % grep -v Ok 594512010405.log [... build steps omitted...] creating sqlite3 ./testfixture ../sqlite/test/quick.test autovacuum-ioerr-1.27.3... Expected: [1] Got: [0] autovacuum-ioerr2-4.34.3... Expected: [1] Got: [0] ioerr-2.187.1... Error: database is locked /[... pwd ...]/594512010405/bld/.libs/testfixture: database is locked while executing "ifcapable vacuum { do_ioerr_test ioerr-2 -cksum true -sqlprep { BEGIN; CREATE TABLE t1(a, b, c); INSERT INTO t1 VALUES(1, randstr(50,..." (file "../sqlite/test/ioerr.test" line 57) invoked from within "source $testfile" ("foreach" body line 4) invoked from within "foreach testfile [lsort -dictionary [glob $testdir/*.test]] { set tail [file tail $testfile] if {[lsearch -exact $EXCLUDE $tail]>=0} continue so..." (file "../sqlite/test/quick.test" line 45) make: *** [test] Error 1
--Steve
On Mar 30, 2005, at 10:08 AM, Jason Jobe wrote:
I don't know if this the right forum for this but I just did a CVS update, built and ran the standard "make test".
10 errors out of 19855 tests
Failures on these tests: autovacuum-ioerr-6.1.1 autovacuum-ioerr-6.2.1 autovacuum-ioerr-6.3.1 autovacuum-ioerr-6.4.1 autovacuum-ioerr-6.5.1 ioerr-6.1.1 ioerr-6.2.1 ioerr-6.3.1 ioerr-6.4.1 ioerr-6.5.1
Is there anything I can do to help narrow down the problem.
-jason