Just to close the loop, with the commit at:
https://www.sqlite.org/src/info/d9e4f9574659c628
All tests now pass cleanly in my environment.
Thank you very much!
--
Sent from: http://sqlite.1065341.n5.nabble.com/
___
sqlite-users mailing list
Thanks, emailed separately with the atachment.
Output from the test run was:
[aiannotti@dog SQLite-6821c61f]$ ./testfixture test/btree02.test
btree02-100... Ok
btree02-110...
! btree02-110 expected: [27]
! btree02-110 got: [20]
SQLite 2018-12-26 18:34:56
Hi Richard,
On Thu, 27 Dec 2018 03:16:24 -0500
Richard Hipp wrote:
> Please patch the btree02.test file as follows:
>
> --- test/btree02.test
> +++ test/btree02.test
> @@ -27,10 +27,11 @@
>CREATE TABLE t3(cnt);
>WITH RECURSIVE c(i) AS (VALUES(1) UNION ALL SELECT i+1 FROM c WHERE i<4)
>
Please patch the btree02.test file as follows:
--- test/btree02.test
+++ test/btree02.test
@@ -27,10 +27,11 @@
CREATE TABLE t3(cnt);
WITH RECURSIVE c(i) AS (VALUES(1) UNION ALL SELECT i+1 FROM c WHERE i<4)
INSERT INTO t3(cnt) SELECT i FROM c;
SELECT count(*) FROM t1;
} {10}
+file
I am seeing the make test fail on btree02-110, are there configuration
directives I should use to use to fix this? (Currently only using the tcl
directory configure flag.)
I am getting this with 3.27.0 and the latest pull from
https://www.sqlite.org/src/info/trunk - SQLite-6821c61f
Running on
5 matches
Mail list logo