[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

STINNER Victor added the comment: David: "Ok, this should be resolved." Oh, thank you! I confirm that test_sqlite3 pass again! -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

Changes by Berker Peksag : -- nosy: +berker.peksag ___ Python tracker ___ ___

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

David Bolen added the comment: Ok, this should be resolved. I opted to be a bit more conservative and only upgraded to sqlite3 3.8.3.1, which is the oldest version still in use for the dmg installer packages (for 2.7). I restarted the most recent 3.x build and while it's not completely done

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

David Bolen added the comment: The test appears to pass against a local test build of sqlite3 3.18.0, so I'll probably just plan on updating the slave to that later tonight. Unless anyone is interested in figuring out why it fails with 3.6.11 and not 3.18.0 (e.g., does the test have a higher

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

David Bolen added the comment: No recent changes to the buildbot (I think the last was in September to bump the local python used to run the slave/build installer to 2.7). The default system sqlite (/usr/lib) is 3.0.8.6, so extremely old, but 3.6.11 is in /usr/local/{lib,include} from early

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

STINNER Victor added the comment: > It seems there might be mismatch between sqlite3_libversion() and > SQLITE_VERSION. I am not familiar with the buildbots but can you run a test > that check that sqlite3_libversion() == SQLITE_VERSION? The Python sqlite3 exports sqlite3_libversion() as

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

Aviv Palivoda added the comment: > It's even more strange. The test started to fail since this build, Sun Apr 9 > 10:10:15 2017: This was merged on Apr 9 (commit 0e6cb2ea624570ed08c354f1ed1f595dab4192d6). >From a quick look in the internet some other people had a similar problem:

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

STINNER Victor added the comment: It's even more strange. The test started to fail since this build, Sun Apr 9 10:10:15 2017: http://buildbot.python.org/all/builders/x86%20Tiger%203.x/builds/528 test_sqlite: testing with version '2.6.0', sqlite_version '3.6.11' ... test test_sqlite failed

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

STINNER Victor added the comment: The test is already skipped on SQLite version older than 3.3.9, no idea why the test fails on SQLite version 3.6.11 on OS X Tiger: @unittest.skipIf(sqlite.sqlite_version_info < (3, 3, 9), "sqlite3_prepare_v2 is not available") I proposed the

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

Changes by STINNER Victor : -- pull_requests: +1356 ___ Python tracker ___ ___

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

STINNER Victor added the comment: SQLite version: Re-running test 'test_sqlite' in verbose mode test_sqlite: testing with version '2.6.0', sqlite_version '3.6.11' -- ___ Python tracker

[issue30126] CheckTraceCallbackContent of test_sqlite3 fails on OS X Tiger

New submission from STINNER Victor: I suggest to skip the following test on OS X Tiger, since it fails but I'm not interested to fix it and it seems to be an old SQLite bug which was fixed after Tiger was released (I don't see this failure on any other buildbot).