Re: wc-queries-test test failure with -DSQLITE_ENABLE_STMT_SCANSTATUS

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: wc-queries-test test failure with -DSQLITE_ENABLE_STMT_SCANSTATUS

Branko Čibej
[Moving to the correct list.]

On 22.01.2019 22:18, Thomas Deutschmann wrote:

> Hi,
>
> in Gentoo Linux, wc-queries-test test is failing (verified
> against v1.9.7-1.11.1:
>
>> START: wc-queries-test
>> DBG: Using Sqlite 3.25.3
>> PASS:  wc-queries-test 1: sqlite up-to-date
>> PASS:  wc-queries-test 2: queries are parsable
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'
>> DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation
>> DBG: Unhandled sqlite operation 'UNION' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'
>> DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation
>> DBG: Unhandled sqlite operation 'UNION' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'
>> DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'UNION' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'
>> DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'UNION' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CO-ROUTINE' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>> DBG: Expected 'TABLE', got 'CONSTANT' in 'SCAN CONSTANT ROW'
>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>> svn_tests: E200006: STMT_FINALIZE_UPDATE_MOVE: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE IF EXISTS update_move_list
>> svn_tests: E200006: STMT_FINALIZE_UPDATE_MOVE: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE IF EXISTS update_move_list
>> svn_tests: E200006: STMT_FINALIZE_UPDATE_MOVE: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE IF EXISTS update_move_list
>> svn_tests: E200006: STMT_FINALIZE_DELETE: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE IF EXISTS delete_list
>> svn_tests: E200006: STMT_FINALIZE_DELETE: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE IF EXISTS delete_list
>> svn_tests: E200006: STMT_FINALIZE_DELETE: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE IF EXISTS delete_list
>> svn_tests: E200006: STMT_DROP_REVERT_LIST: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE IF EXISTS revert_list
>> svn_tests: E200006: STMT_DROP_REVERT_LIST: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE IF EXISTS revert_list
>> svn_tests: E200006: STMT_DROP_REVERT_LIST: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE IF EXISTS revert_list
>> svn_tests: E200006: STMT_DROP_TARGETS_LIST: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE targets_list
>> svn_tests: E200006: STMT_DROP_TARGETS_LIST: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE targets_list
>> svn_tests: E200006: STMT_DROP_TARGETS_LIST: Uses sqlite_master with only 0 index component: ((null))
>> DROP TABLE targets_list
>> svn_tests: E200042: Additional errors:
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> svn_tests: E200035: |SCAN TABLE sqlite_master
>> FAIL:  wc-queries-test 3: test query expectations
>> PASS:  wc-queries-test 4: test query duplicates
>> PASS:  wc-queries-test 5: test schema statistics
>> PASS:  wc-queries-test 6: verify queries are parsable
>> END: wc-queries-test
>> ELAPSED: wc-queries-test 0:00:00.167083
> After some research we found the problem causing the test failure:
>
> In Gentoo we are building sqlite with
>
>> -DSQLITE_ENABLE_STMT_SCANSTATUS
> option set. If we disable that option, the test is passing.
>
> Downstream-bug: https://bugs.gentoo.org/605438
>
>

Reply | Threaded
Open this post in threaded view
|

Re: wc-queries-test test failure with -DSQLITE_ENABLE_STMT_SCANSTATUS

Branko Čibej
On 22.01.2019 22:52, Branko Čibej wrote:

> [Moving to the correct list.]
>
> On 22.01.2019 22:18, Thomas Deutschmann wrote:
>> Hi,
>>
>> in Gentoo Linux, wc-queries-test test is failing (verified
>> against v1.9.7-1.11.1:
>>
>>> START: wc-queries-test
>>> DBG: Using Sqlite 3.25.3
>>> PASS:  wc-queries-test 1: sqlite up-to-date
>>> PASS:  wc-queries-test 2: queries are parsable
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'
>>> DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation
>>> DBG: Unhandled sqlite operation 'UNION' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'
>>> DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation
>>> DBG: Unhandled sqlite operation 'UNION' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'
>>> DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'UNION' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'SCALAR' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'
>>> DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'UNION' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CO-ROUTINE' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>>> DBG: Expected 'TABLE', got 'CONSTANT' in 'SCAN CONSTANT ROW'
>>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MERGE' in explanation
>>> DBG: Unhandled sqlite operation 'LEFT' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'RIGHT' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> DBG: Unhandled sqlite operation 'CORRELATED' in explanation
>>> DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation
>>> svn_tests: E200006: STMT_FINALIZE_UPDATE_MOVE: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE IF EXISTS update_move_list
>>> svn_tests: E200006: STMT_FINALIZE_UPDATE_MOVE: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE IF EXISTS update_move_list
>>> svn_tests: E200006: STMT_FINALIZE_UPDATE_MOVE: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE IF EXISTS update_move_list
>>> svn_tests: E200006: STMT_FINALIZE_DELETE: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE IF EXISTS delete_list
>>> svn_tests: E200006: STMT_FINALIZE_DELETE: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE IF EXISTS delete_list
>>> svn_tests: E200006: STMT_FINALIZE_DELETE: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE IF EXISTS delete_list
>>> svn_tests: E200006: STMT_DROP_REVERT_LIST: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE IF EXISTS revert_list
>>> svn_tests: E200006: STMT_DROP_REVERT_LIST: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE IF EXISTS revert_list
>>> svn_tests: E200006: STMT_DROP_REVERT_LIST: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE IF EXISTS revert_list
>>> svn_tests: E200006: STMT_DROP_TARGETS_LIST: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE targets_list
>>> svn_tests: E200006: STMT_DROP_TARGETS_LIST: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE targets_list
>>> svn_tests: E200006: STMT_DROP_TARGETS_LIST: Uses sqlite_master with only 0 index component: ((null))
>>> DROP TABLE targets_list
>>> svn_tests: E200042: Additional errors:
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>> FAIL:  wc-queries-test 3: test query expectations
>>> PASS:  wc-queries-test 4: test query duplicates
>>> PASS:  wc-queries-test 5: test schema statistics
>>> PASS:  wc-queries-test 6: verify queries are parsable
>>> END: wc-queries-test
>>> ELAPSED: wc-queries-test 0:00:00.167083
>> After some research we found the problem causing the test failure:
>>
>> In Gentoo we are building sqlite with
>>
>>> -DSQLITE_ENABLE_STMT_SCANSTATUS
>> option set. If we disable that option, the test is passing.
>>
>> Downstream-bug: https://bugs.gentoo.org/605438


I've filed this as issue #4804, it looks like a bug in our tests.

-- Brane

Reply | Threaded
Open this post in threaded view
|

Re: wc-queries-test test failure with -DSQLITE_ENABLE_STMT_SCANSTATUS

Branko Čibej
On 22.01.2019 23:10, Branko Čibej wrote:
> On 22.01.2019 22:52, Branko Čibej wrote:
>> [Moving to the correct list.]
>>
>> On 22.01.2019 22:18, Thomas Deutschmann wrote:
>>> Hi,
>>>
>>> in Gentoo Linux, wc-queries-test test is failing (verified
>>> against v1.9.7-1.11.1:
>>>
[...]

>>>> svn_tests: E200006: STMT_DROP_TARGETS_LIST: Uses sqlite_master with only 0 index component: ((null))
>>>> DROP TABLE targets_list
>>>> svn_tests: E200042: Additional errors:
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>> FAIL:  wc-queries-test 3: test query expectations
>>>> PASS:  wc-queries-test 4: test query duplicates
>>>> PASS:  wc-queries-test 5: test schema statistics
>>>> PASS:  wc-queries-test 6: verify queries are parsable
>>>> END: wc-queries-test
>>>> ELAPSED: wc-queries-test 0:00:00.167083
>>> After some research we found the problem causing the test failure:
>>>
>>> In Gentoo we are building sqlite with
>>>
>>>> -DSQLITE_ENABLE_STMT_SCANSTATUS
>>> option set. If we disable that option, the test is passing.
>>>
>>> Downstream-bug: https://bugs.gentoo.org/605438
>
> I've filed this as issue #4804, it looks like a bug in our tests.


I was able to reproduce this with the latest (amalgamated) SQLite on
macOS — so, not using get-deps.sh, as the version that downloads is too
old. I've written up my analysis in issue #4804; the short story is that
adding the compile-time option mentioned above adds output to 'EXPLAIN
QUERY PLAN' that our test doesn't like.

Bert, you wrote most of this query test code; would you mind taking a
look at this issue?

-- Brane

Reply | Threaded
Open this post in threaded view
|

Re: wc-queries-test test failure with -DSQLITE_ENABLE_STMT_SCANSTATUS

Branko Čibej
On 23.01.2019 04:34, Branko Čibej wrote:

> On 22.01.2019 23:10, Branko Čibej wrote:
>> On 22.01.2019 22:52, Branko Čibej wrote:
>>> [Moving to the correct list.]
>>>
>>> On 22.01.2019 22:18, Thomas Deutschmann wrote:
>>>> Hi,
>>>>
>>>> in Gentoo Linux, wc-queries-test test is failing (verified
>>>> against v1.9.7-1.11.1:
>>>>
> [...]
>>>>> svn_tests: E200006: STMT_DROP_TARGETS_LIST: Uses sqlite_master with only 0 index component: ((null))
>>>>> DROP TABLE targets_list
>>>>> svn_tests: E200042: Additional errors:
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> svn_tests: E200035: |SCAN TABLE sqlite_master
>>>>> FAIL:  wc-queries-test 3: test query expectations
>>>>> PASS:  wc-queries-test 4: test query duplicates
>>>>> PASS:  wc-queries-test 5: test schema statistics
>>>>> PASS:  wc-queries-test 6: verify queries are parsable
>>>>> END: wc-queries-test
>>>>> ELAPSED: wc-queries-test 0:00:00.167083
>>>> After some research we found the problem causing the test failure:
>>>>
>>>> In Gentoo we are building sqlite with
>>>>
>>>>> -DSQLITE_ENABLE_STMT_SCANSTATUS
>>>> option set. If we disable that option, the test is passing.
>>>>
>>>> Downstream-bug: https://bugs.gentoo.org/605438
>> I've filed this as issue #4804, it looks like a bug in our tests.
>
> I was able to reproduce this with the latest (amalgamated) SQLite on
> macOS — so, not using get-deps.sh, as the version that downloads is too
> old. I've written up my analysis in issue #4804; the short story is that
> adding the compile-time option mentioned above adds output to 'EXPLAIN
> QUERY PLAN' that our test doesn't like.
>
> Bert, you wrote most of this query test code; would you mind taking a
> look at this issue?

I decided to "fix" this by ignoring it ... see r1852013. I think the fix
is correct, given what the test is supposed to do.

-- Brane