[Python-Dev] Committing bsddb 4.6.4, and where can I put testsuite temp files? (original) (raw)

Gregory P. Smith greg at krypto.org
Wed May 14 06:33:47 CEST 2008

btw, I fixed the Lib/test/test_bsddb3.py file for the updated Lib/bsddb/test/ modules. Thats how the test suite gets run by the buildbots (run the test suite from a python trunk sandbox using "./python Lib/test/regrtest.py -v -u bsddb test_bsddb test_bsddb3" to reproduce exactly how it is run yourself).

I'm seeing what appears to be a memory corruption error when using a debug build of trunk (configure --with-pydebug). It causes a crash while deallocating the argument tuple passed to DBEnv.lock_get on the second call in bsddb.test.test_lock's test03_lock_timeout() test. Platform tested on: OS X 10.4, gcc 4.0.1 x86. BerkeleyDB 4.5.

I haven't tested on other platforms but I expect other buildbots will also have issues now that the test suite isn't being skipped.

-gps

On Tue, May 13, 2008 at 12:09 PM, Jesus Cea <jcea at jcea.es> wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

I just committed pybsddb 4.6.4 to python svn. My next step (after a successfull buildbot cycle, I hope!) is to commit the new testsuite. First I need to review any changes there since I maintain pybsddb. The testsuite creates a lot of files/directories while working. Fine, since it cleans later, unless some test crashes hard. My testcode defines a variable to the path I want to use to keep those files/dirs. Currently it is "/tmp/z-BerkeleyDB", or something like that. Since my code allows for testcases to be run in multiple threads and/or processes, where would be a sensible path choice for temporal files?. Current working directory would be fine, if "somebody" is cleaning after running all tests. Ramdisk ("/tmp" in some systems, for example Solaris) would be nice, since some test uses transactions, and transactions are write-synchronous. In my system, runnning all tests serially (you can run all of them in parallel, if you wish) takes about 15-20 seconds. Far faster than current tests in python svn, and that can be improved even more. - -- Jesus Cea Avion // /// /// jcea at jcea.es - http://www.jcea.es/ // // // // // jabber / xmpp:jcea at jabber.org // // ///// ~ // // // // // "Things are not so easy" // // // // // // "My name is Dump, Core Dump" /// /// // // "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBSCnngZlgi5GaxT1NAQLhPwP9GMMyNMgz6mfmfHXVOV8bDJGOQRok95uL 14A+K9zXW3/wlp1rhvoPmCHYqvRoCLVkPZ/7pLEQlo1ZksOlHy6BH3MDeDJEjVax 69XlzUUeuqplGbTiMdX8qd0dPi2Jp+Akg7U6ZmBdADhF7D21umU474OalKO2eIoL ba/wnlMvens= =1lai -----END PGP SIGNATURE-----

Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/greg%40krypto.org

More information about the Python-Dev mailing list