[pybsddb] Re: [Python-Dev] Looking for a Windows bsddb fan

[Gregory P. Smith]

I don't get these errors under linux or windows using the latest pybsddb
cvs and python 2.2.2.  (berkeleydb 4.1.25)

Occasionally there are DBDeadlockErrors that come up in the threading
tests (more often on windows) but they are appropriate and non fatal to
the tests.

I haven't tried python 2.3a from cvs.

Can you verify that the build/db_home directory created to use for the
test DB environment & DB files is cleared out when you run test.py (i
believe part of the unit tests themselves removes the entire directory
and contents; but I remember errors long ago that were due to using an
old messed up DB environment rather than a fresh one)

-G

On Fri, Jan 24, 2003 at 08:58:01AM -0500, Barry A. Warsaw wrote:
> 
> >>>>> "BAW" == Barry A Warsaw <barry@python.org> writes:
> 
>     BAW> I forwarded this message to pybsddb-users@lists.sf.net.  I'm
>     BAW> not sure if Greg Smith reads python-dev and he's probably the
>     BAW> best guy to look at Windows problems.  Needless to say, the
>     BAW> extended tests work(ed) fine for me on Linux.
> 
> I take that back, I'm getting similar failures on Linux after
> cvs upping and rebuilding with db 4.1.25.
> 
> Will investigate.
> -Barry
> 
> -------------------- snip snip --------------------
> ...
> ======================================================================
> ERROR: test01_associateWithDB (bsddb.test.test_associate.ThreadedAssociateRecnoTestCase)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/home/barry/projects/python/Lib/bsddb/test/test_associate.py", line 96, in setUp
>     self.env.open(homeDir, db.DB_CREATE | db.DB_INIT_MPOOL |
> DBAgainError: (11, 'Resource temporarily unavailable -- unable to join the environment')

...