Re: [Python-Dev] Massive test_sqlite failure on Mac OSX ... sometimes
On Oct 21, 2006, at 8:03 PM, [EMAIL PROTECTED] wrote: Followup #2... Yesterday I whittled my problems with test_sqlite on my OSX g5 to test_ctypes and test_sqlite: ./python.exe Lib/test/regrtest.py -l -f tests test_ctypes test_sqlite test test_sqlite failed -- errors occurred; run in verbose mode for details 1 test OK. 1 test failed: test_sqlite Today I refined things further. I renamed all the test_*.py files in Lib/ctypes/test/ until all I was left with was test_find.py. It fails if that's the only ctypes test script run: $ ls -l *.py -rw--- 1 buildbot buildbot 6870 Oct 20 06:30 __init__.py -rw--- 1 buildbot buildbot 624 Oct 20 06:30 runtests.py -rw--- 1 buildbot buildbot 3463 Oct 21 12:52 test_find.py montanaro:~/pybot/trunk.montanaro-g5/build/Lib/ctypes/test buildbot$ cd - /Library/Buildbot/pybot/trunk.montanaro-g5/build montanaro:~/pybot/trunk.montanaro-g5/build buildbot$ ./ python.exe Lib/test/regrtest.py -l -f tests test_ctypes test_sqlite test test_sqlite failed -- errors occurred; run in verbose mode for details 1 test OK. 1 test failed: test_sqlite test_find.py contains checks for three OpenGL libraries on darwin: gl, glu and glut. If I comment out all those tests, test_sqlite succeeds. If any of them are enabled, test_sqlite fails. According to a comment in (IIRC) the pyOpenGL sources GLUT on OSX does a chdir() during initialization, that could be the problem here. Ronald smime.p7s Description: S/MIME cryptographic signature ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Massive test_sqlite failure on Mac OSX ... sometimes
Ronald According to a comment in (IIRC) the pyOpenGL sources GLUT on Ronald OSX does a chdir() during initialization, that could be the Ronald problem here. How would that explain that it fails on my g5 but not on my powerbook? They are at the same revision of the operating system and compiler. The checksums on the libraries are different though the file sizes are the same. The dates on the files are different as well. I suspect the checksum difference is caused by the different upgrade dates of the two machines and the resulting different times the two systems were optimized. Is there anyone else with a g5 who can do a vanilla Unix (not framework) build on an up-to-date g5 from an up-to-date Subversion repository? It would be nice if someone else could at least confirm or not confirm this problem. Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Massive test_sqlite failure on Mac OSX ... sometimes
On Sun, 22 Oct 2006 07:51:27 -0500, [EMAIL PROTECTED] wrote: Ronald According to a comment in (IIRC) the pyOpenGL sources GLUT on Ronald OSX does a chdir() during initialization, that could be the Ronald problem here. How would that explain that it fails on my g5 but not on my powerbook? They are at the same revision of the operating system and compiler. The checksums on the libraries are different though the file sizes are the same. The dates on the files are different as well. I suspect the checksum difference is caused by the different upgrade dates of the two machines and the resulting different times the two systems were optimized. Is there anyone else with a g5 who can do a vanilla Unix (not framework) build on an up-to-date g5 from an up-to-date Subversion repository? It would be nice if someone else could at least confirm or not confirm this problem. Robert Gravina has seen a problem which bears some resemblance to this one while using PySQLite in a real application on OS X. I've pointed him to this thread; hopefully it's the same issue and a second way of producing the issue will shed some more light on the matter. The top of that thread is available here: http://divmod.org/users/mailman.twistd/pipermail/divmod-dev/2006-October/000707.html Jean-Paul ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Massive test_sqlite failure on Mac OSX ... sometimes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 22, 2006, at 8:51 AM, [EMAIL PROTECTED] wrote: Is there anyone else with a g5 who can do a vanilla Unix (not framework) build on an up-to-date g5 from an up-to-date Subversion repository? It would be nice if someone else could at least confirm or not confirm this problem. By vanilla unix you mean a pretty simple ./configure; make; make test? Works for me with Python 2.5 on both my G5s and Intel Macs, all running 10.4.8. Note though that I usually build with CPPFLAGS and LDFLAGS pointing to /opt/local in order to pick up DarwinPorts readline, and you do the same and have a version of sqlite from there you can have problems. For example, we were seeing some very odd infloops in our sqlite layer. We have our own version of sqlite that we expected to be dynamically linked against, but when I used otool -L to check it, I realized we were dynamically linked against a version of sqlite in DarwinPorts. Getting rid of the unnecessary DarwinPorts version and making sure that we were dynamically linking against our version eliminated the infloops. What do you get when you check _sqlite3? % otool -L build/lib.macosx-10.3-ppc-2.5/_sqlite3.so build/lib.macosx-10.3-ppc-2.5/_sqlite3.so: /usr/lib/libsqlite3.0.dylib (compatibility version 9.0.0, current version 9.6.0) /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 92.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.7) Any possibility something like that's going on? - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRTwSqHEjvBPtnXfVAQLvwQP/VuTQwwXwsauiuQt8E3k05scWsykarLaZ YMJyVwq++DH/X8C5RODG9seYhSMQLF8PKMStmhKWLmlQ9mfFPIobMgsFqXBuI+bD njUOh74O6vcJw1RNKXaERdQ6ABb2t79S6w+Psu5hGOP1NDy/e9GQazw05HpJWWvG 7Py+bDt24oE= =9TjL -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Massive test_sqlite failure on Mac OSX ... sometimes
Barry What do you get when you check _sqlite3? $ otool -L ./build/lib.mac-10.3-ppc-2.6/_sqlite3.so ./build/lib.macosx-10.3-ppc-2.6/_sqlite3.so: /usr/local/lib/libsqlite3.0.dylib (compatibility version 9.0.0, current version 9.6.0) /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 93.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.7) Which I apparently installed on Oct 15 but seem to have forgotten... According to the source in my directory, it's sqlite 3.3.8. On my powerbook it's linked against /usr/lib/libsqlite3.0.dylib... Make clean, run the failing test pair, now it's fine. Otool shows linkage against /usr/lib/libsqlite3.0.dylib...: $ otool -L ./build/lib.macosx-10.3-ppc-2.6/_sqlite3.so ./build/lib.macosx-10.3-ppc-2.6/_sqlite3.so: /usr/lib/libsqlite3.0.dylib (compatibility version 9.0.0, current version 9.6.0) /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 93.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.7) According to /usr/include/sqlite3.h, what's installed by Apple is 3.1.3. Aside from the possibility that I somehow compiled against /usr/include/sqlite3.h and linked against /usr/local/lib/libsqlite3.0.dylib, what difference should 3.3.8 vs. 3.1.3 have made? Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Massive test_sqlite failure on Mac OSX ... sometimes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 22, 2006, at 11:24 PM, [EMAIL PROTECTED] wrote: According to /usr/include/sqlite3.h, what's installed by Apple is 3.1.3. Aside from the possibility that I somehow compiled against /usr/include/sqlite3.h and linked against /usr/local/lib/ libsqlite3.0.dylib, what difference should 3.3.8 vs. 3.1.3 have made? Dunno, but as much as I love SQLite, I've also found it to be pretty finicky. For example, I once tried to upgrade us from 3.2.1 to 3.2.8 but that caused us a world of hurt, so I reverted back to the last known good version. At some point I'll try to get us on the latest release, but I'm a little gunshy about it. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRTw8e3EjvBPtnXfVAQJbKgP+MjAz/NfUOaDd+ZEg9haJVr7v5JsKTHEl i9n7pLLFToIE81RX3iGHMZwIZyIGHqT9d3gqan8INrvcAtL7hxVvkqAAFRJTmX2Z XVLAjWLYCp9nY6Q3K+yXls798RDoHhZIWvHnNXZJ7Ya2wwSVQoADFdV1GN0pIB07 PnNHa/S83+Q= =4fX8 -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Massive test_sqlite failure on Mac OSX ... sometimes
Followup #2... Yesterday I whittled my problems with test_sqlite on my OSX g5 to test_ctypes and test_sqlite: ./python.exe Lib/test/regrtest.py -l -f tests test_ctypes test_sqlite test test_sqlite failed -- errors occurred; run in verbose mode for details 1 test OK. 1 test failed: test_sqlite Today I refined things further. I renamed all the test_*.py files in Lib/ctypes/test/ until all I was left with was test_find.py. It fails if that's the only ctypes test script run: $ ls -l *.py -rw--- 1 buildbot buildbot 6870 Oct 20 06:30 __init__.py -rw--- 1 buildbot buildbot 624 Oct 20 06:30 runtests.py -rw--- 1 buildbot buildbot 3463 Oct 21 12:52 test_find.py montanaro:~/pybot/trunk.montanaro-g5/build/Lib/ctypes/test buildbot$ cd - /Library/Buildbot/pybot/trunk.montanaro-g5/build montanaro:~/pybot/trunk.montanaro-g5/build buildbot$ ./python.exe Lib/test/regrtest.py -l -f tests test_ctypes test_sqlite test test_sqlite failed -- errors occurred; run in verbose mode for details 1 test OK. 1 test failed: test_sqlite test_find.py contains checks for three OpenGL libraries on darwin: gl, glu and glut. If I comment out all those tests, test_sqlite succeeds. If any of them are enabled, test_sqlite fails. I've taken this about as far as I can. I submitted a bug report here: http://python.org/sf/1581906 Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Massive test_sqlite failure on Mac OSX ... sometimes
I'm setting up a buildbot slave for sqlalchemy on one of my Macs at home. When it builds and tests Python's test suite the sqlite test fails. When I ran it alone like this: ./python.exe Lib/test/test_sqlite.py and ./python.exe Lib/test/regrtest.py test_sqlite it succeeded. When I ran the full test suite it failed. I then tried adding -v as the error message suggested. It hung in test_pty waiting for a child process to complete. (Is this a known problem?) I finally redirected stdout and stderr like so: ./python.exe Lib/test/regrtest.py -l -v test.out 21 and it completed. It failed 146 out of 167 tests. Here is a sample of the failure messages: ... CheckClose (sqlite3.test.dbapi.ConnectionTests) ... ERROR CheckCommit (sqlite3.test.dbapi.ConnectionTests) ... ERROR CheckCommitAfterNoChanges (sqlite3.test.dbapi.ConnectionTests) ... ERROR CheckCursor (sqlite3.test.dbapi.ConnectionTests) ... ERROR CheckExceptions (sqlite3.test.dbapi.ConnectionTests) ... ERROR CheckFailedOpen (sqlite3.test.dbapi.ConnectionTests) ... ERROR CheckRollback (sqlite3.test.dbapi.ConnectionTests) ... ERROR CheckRollbackAfterNoChanges (sqlite3.test.dbapi.ConnectionTests) ... ERROR CheckArraySize (sqlite3.test.dbapi.CursorTests) ... ERROR CheckClose (sqlite3.test.dbapi.CursorTests) ... ERROR CheckCursorConnection (sqlite3.test.dbapi.CursorTests) ... ERROR CheckCursorWrongClass (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteArgFloat (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteArgInt (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteArgString (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteDictMapping (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteDictMappingNoArgs (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteDictMappingTooLittleArgs (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteDictMappingUnnamed (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteIllegalSql (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteManyGenerator (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteManyIterator (sqlite3.test.dbapi.CursorTests) ... ERROR CheckExecuteManyNotIterable (sqlite3.test.dbapi.CursorTests) ... ERROR ... A quick check of the tracebacks shows all the errors are of this form (CheckClose is the first failure): == ERROR: CheckClose (sqlite3.test.dbapi.ConnectionTests) -- Traceback (most recent call last): File /Library/Buildbot/pybot/trunk.montanaro-g5/build/Lib/sqlite3/test/dbapi.py, line 85, in setUp self.cx = sqlite.connect(:memory:) ProgrammingError: library routine called out of sequence That is, they all raise the same exception and all exceptions are raised on sqlite.connect(:memory:) calls. Sometimes there is a second parameter to the call. Anybody seen this before? Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Massive test_sqlite failure on Mac OSX ... sometimes
Following up on my earlier post... I svn up'd both my g5 and my g4 powerbook (both running OSX 10.4.8, gcc 4.0.0 apple build 5026), built and tested both. The test suite completed fine on my powerbook, failed on the g5. I tried running regrtest.py twice more on the g5 with the -r flag. It failed the first time, succeeded the second. I then made a series of run with the -f flag (thank you once again for that Señor Peters). I whittled it down to the following reliably failing pair: $ ./python.exe Lib/test/regrtest.py -l -f tests test_ctypes test_sqlite test test_sqlite failed -- errors occurred; run in verbose mode for details 1 test OK. 1 test failed: test_sqlite For confirmation, this pair works fine on my g4 powerbook. I've gone no further so far. It's bedtime. Maybe someone else can at least try to reproduce what I've come up with so far on other platforms or on another Mac g5. Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
