This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Andreas.Stieger
Recipients Andreas.Stieger
Date 2014-03-12.21:51:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394661104.86.0.58139727656.issue20901@psf.upfronthosting.co.za>
In-reply-to
Content
SQLite 3.8.4 fails test_sqlite on 2.7 and 3.4.

[ 296s] test test_sqlite failed -- Traceback (most recent call last):
[ 296s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.6/Lib/sqlite3/test/hooks.py", line 165, in CheckOpcodeCount
[ 296s] self.assertTrue(first_count > second_count)
[ 296s] AssertionError: False is not true

This seems to be a change in behaviour callback of SQLite: (one "." per callback issued)
sqlite3_progress_handler(db, 1, progress_callback, NULL);
sqlite3_exec(db, "create table foo(a,b)", callback, 0, &zErrMsg);
sqlite3_progress_handler(db, 2, progress_callback, NULL);
sqlite3_exec(db, "create table bar(a,b)", callback, 0, &zErrMsg);

3.7.17> ./test
..................................................................
...........................
3.8.3.1> ./test
........
.......
3.8.4> ./test
.....
.....
3.8.4.1> ./test
.....
.....

This may be a side effect of optimization Documentation does day the callbacks are approximate. Can the test be adjusted to run more than CREATE TABLE so that a difference in the number of callbacks is tested for?

Also see openSUSE bug: https://bugzilla.novell.com/show_bug.cgi?id=867887
History
Date User Action Args
2014-03-12 21:51:44Andreas.Stiegersetrecipients: + Andreas.Stieger
2014-03-12 21:51:44Andreas.Stiegersetmessageid: <1394661104.86.0.58139727656.issue20901@psf.upfronthosting.co.za>
2014-03-12 21:51:44Andreas.Stiegerlinkissue20901 messages
2014-03-12 21:51:44Andreas.Stiegercreate