Issue 1010645: bsddb3 testsuite failure when running more than one time (original) (raw)

Issue1010645

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/40771

classification

Title: bsddb3 testsuite failure when running more than one time
Type: Stage:
Components: Extension Modules Versions: Python 2.5

process

Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: gregory.p.smith Nosy List: doko, gregory.p.smith, jcea
Priority: normal Keywords:

Created on 2004-08-17 10:39 by doko, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg22097 - (view) Author: Matthias Klose (doko) * (Python committer) Date: 2004-08-17 10:39
running the testsuite with TESTOPTS="-l -unetwork,bsddb" leaves (sometimes?) an directory Lib/test/db_home, which lets two of the bsddb tests fail in further test runs. Removing this directory before the next test run, lets the tests complete sucessfully.
msg22098 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2006-04-12 20:44
Logged In: YES user_id=413 yes there appear to be several messy turds (db_home/ and even a db created outside of db_home) in the existing full bsddb test suite. its on my list to find and clean up.
msg66979 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2008-05-17 06:57
I believe this was finally cleaned up. There are still changes to be made to the current test suite (blindly using a directory under /tmp and not cleaning it up afterwards is bad) but the actual bug this refers to was fixed.
History
Date User Action Args
2022-04-11 14:56:06 admin set github: 40771
2008-05-17 06:57:41 gregory.p.smith set status: open -> closedresolution: fixedmessages: +
2008-03-10 18:29:13 jcea set nosy: + jcea
2004-08-17 10:39:13 doko create