bsddb3 testsuite failure when running more than one time

[doko42]

BPO	1010645
Nosy	@doko42, @gpshead, @jcea

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/gpshead'
closed_at = <Date 2008-05-17.06:57:41.169>
created_at = <Date 2004-08-17.10:39:13.000>
labels = ['extension-modules']
title = 'bsddb3 testsuite failure when running more than one time'
updated_at = <Date 2008-05-17.06:57:41.162>
user = 'https://github.com/doko42'

bugs.python.org fields:

activity = <Date 2008-05-17.06:57:41.162>
actor = 'gregory.p.smith'
assignee = 'gregory.p.smith'
closed = True
closed_date = <Date 2008-05-17.06:57:41.169>
closer = 'gregory.p.smith'
components = ['Extension Modules']
creation = <Date 2004-08-17.10:39:13.000>
creator = 'doko'
dependencies = []
files = []
hgrepos = []
issue_num = 1010645
keywords = []
message_count = 3.0
messages = ['22097', '22098', '66979']
nosy_count = 3.0
nosy_names = ['doko', 'gregory.p.smith', 'jcea']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1010645'
versions = ['Python 2.5']

[doko42]

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.

[gpshead]

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.

[gpshead]

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.