Lines Matching refs:XXX

89     XXX Should we compile with OPTS=threads?
105     XXX Should we compile with OPTS=threads?
107     XXX I have no idea whether "nmake -f makefile.vc test" passed or
108     XXX failed.  It popped up tons of little windows, and did lots of
109     XXX stuff, and nothing blew up.
161     XXX The test_bsddb3 tests don't always pass, on Windows (according to
162     XXX me) or on Linux (according to Barry).  (I had much better luck
163     XXX on Win2K than on Win98SE.)  The common failure mode across platforms
164     XXX is
165     XXX     DBAgainError: (11, 'Resource temporarily unavailable -- unable
166     XXX                         to join the environment')
167     XXX
168     XXX and it appears timing-dependent.  On Win2K I also saw this once:
169     XXX
170     XXX test02_SimpleLocks (bsddb.test.test_thread.HashSimpleThreaded) ...
171     XXX Exception in thread reader 1:
172     XXX Traceback (most recent call last):
173     XXX File "C:\Code\python\lib\threading.py", line 411, in __bootstrap
174     XXX    self.run()
175     XXX File "C:\Code\python\lib\threading.py", line 399, in run
176     XXX    apply(self.__target, self.__args, self.__kwargs)
177     XXX File "C:\Code\python\lib\bsddb\test\test_thread.py", line 268, in
178     XXX                  readerThread
179     XXX    rec = c.next()
180     XXX DBLockDeadlockError: (-30996, 'DB_LOCK_DEADLOCK: Locker killed
181     XXX                                to resolve a deadlock')
182     XXX
183     XXX I'm told that DBLockDeadlockError is expected at times.  It
184     XXX doesn't cause a test to fail when it happens (exceptions in
185     XXX threads are invisible to unittest).