[Python-Dev] bsddb3 test errors - are these expected?
Tue, 11 Mar 2003 21:15:38 -0500
> I just tried running regrtest with "-uall,-largefile" (after a "cvs up",
> "./config.status --recheck", and "make") on my Mac OS X system.
> It chugged for awhile, then spit this out several times:
> Exception in thread reader 4:
> Traceback (most recent call last):
> "/Users/skip/src/python/head/dist/src/Lib/threading.py", line
> 411, in __bootstrap
> "/Users/skip/src/python/head/dist/src/Lib/threading.py", line 399, in run
> self.__target(*self.__args, **self.__kwargs)
> y", line 270, in reade
> rec = c.first()
> DBLockDeadlockError: (-30995, 'DB_LOCK_DEADLOCK: Locker
> killed to resolve a deadlock')
> once for each thread,
I believe those are timing-related and harmless. It would be better if the
test suite suppressed such msgs, if so.
> then this:
> RuntimeWarning: DB_INCOMPLETE: Ca
> che flush was unable to complete
> return function(*_args, **_kwargs)
That's not good, though.
> After chugging awhile longer, it segfaulted.
> What (if anything) can I do to provide useful inputs to someone who can
> possibly fix the problem?
Sorry, no idea. Is the pybsddb SF project still open for business?