Hi Matthias, On Mon, Sep 27, 2010 at 19:17:28 +0200, Julien Cristau wrote:
> On Sun, Apr 4, 2010 at 03:06:27 +0200, Matthias Klose wrote: > > > 2.6 used 4.8. an option would be a backport of the 2.6 module > > including the patches to the 2.5 package; such a patch should only > > be applied after 2.6 is the default. > > > I tried to do this, came up with the attached patches. The build log is > at http://people.debian.org/~jcristau/python2.5-db4.8.log and shows > errors from test_bsddb3 (specifically Lib/bsddb/test/test_thread.py) in > some of the runs. Not sure where to go from there. Looking at buildd > logs, either the python2.6 builds nor those from python-bsddb3 seem to > run those tests, so I don't have anything to compare this to. > I re-enabled the bsddb3 test in python2.6's debian/rules, and I see what looks like the same error (again on i386): test_bsddb3 Berkeley DB 4.8.30: (April 9, 2010) Test path prefix: /tmp/z-test_bsddb3-28161 Exception in thread reader 1: Traceback (most recent call last): File "/home/julien/tmp/python2.6-2.6.6/Lib/threading.py", line 532, in __bootstrap_inner self.run() File "/home/julien/tmp/python2.6-2.6.6/Lib/threading.py", line 484, in run self.__target(*self.__args, **self.__kwargs) File "/home/julien/tmp/python2.6-2.6.6/Lib/bsddb/test/test_thread.py", line 306, in readerThread rec = dbutils.DeadlockWrap(c.next, max_retries=10) File "/home/julien/tmp/python2.6-2.6.6/Lib/bsddb/dbutils.py", line 68, in DeadlockWrap return function(*_args, **_kwargs) DBLockDeadlockError: (-30994, 'DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock') Do you think that's enough to consider the switch to 4.8 for python2.5? Should I upload to experimental to get more testing on other architectures first? Cheers, Julien
signature.asc
Description: Digital signature
