➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: BSD DB test failures for BSD DB 3.2
Type: Stage:
Components: Extension Modules Versions:
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: gregory.p.smith Nosy List: gregory.p.smith, nnorwitz
Priority: high Keywords:

Created on 2005-10-20 04:41 by nnorwitz, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
bsddb-bt.txt nnorwitz, 2005-10-20 05:18 bsddb 3.2 backtrace
Messages (6)
msg26637 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2005-10-20 04:41 
After a bunch of modifications to build and get bsddb
mostly running, I still get 4 test failures with Python
2.4 and CVS head.

FAIL: test_previous_last_looping
(test.test_bsddb.TestBTree)
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"/home/neal/build/python/dist/clean/Lib/test/test_bsddb.py",
line 128, in test_previous_last_looping
    self.assertSetEquals(items, self.d.items())
  File
"/home/neal/build/python/dist/clean/Lib/test/test_bsddb.py",
line 55, in assertSetEquals
    self.assertEqual(Set(seqn1), Set(seqn2))
AssertionError: Set([('e', 'Rossum'), ('r',
'invented'), ('q', 'Guido'), ('w', 'van'), ('t',
'Python'), ('y', None)]) != Set([('e', 'Rossum'), ('r',
'invented'), ('t', 'Python'), ('w', 'van'), ('q',
'Guido'), ('y', '')])

======================================================================
FAIL: test_previous_last_looping
(test.test_bsddb.TestHashTable)
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"/home/neal/build/python/dist/clean/Lib/test/test_bsddb.py",
line 128, in test_previous_last_looping
    self.assertSetEquals(items, self.d.items())
  File
"/home/neal/build/python/dist/clean/Lib/test/test_bsddb.py",
line 55, in assertSetEquals
    self.assertEqual(Set(seqn1), Set(seqn2))
AssertionError: Set([('e', 'Rossum'), ('r',
'invented'), ('t', 'Python'), ('w', 'van'), ('q',
'Guido'), ('y', None)]) != Set([('e', 'Rossum'), ('r',
'invented'), ('t', 'Python'), ('w', 'van'), ('q',
'Guido'), ('y', '')])

======================================================================
FAIL: test_previous_last_looping
(test.test_bsddb.TestBTree_InMemory)
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"/home/neal/build/python/dist/clean/Lib/test/test_bsddb.py",
line 128, in test_previous_last_looping
    self.assertSetEquals(items, self.d.items())
  File
"/home/neal/build/python/dist/clean/Lib/test/test_bsddb.py",
line 55, in assertSetEquals
    self.assertEqual(Set(seqn1), Set(seqn2))
AssertionError: Set([('e', 'Rossum'), ('r',
'invented'), ('q', 'Guido'), ('w', 'van'), ('t',
'Python'), ('y', None)]) != Set([('e', 'Rossum'), ('r',
'invented'), ('t', 'Python'), ('w', 'van'), ('q',
'Guido'), ('y', '')])

======================================================================
FAIL: test_previous_last_looping
(test.test_bsddb.TestHashTable_InMemory)
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"/home/neal/build/python/dist/clean/Lib/test/test_bsddb.py",
line 128, in test_previous_last_looping
    self.assertSetEquals(items, self.d.items())
  File
"/home/neal/build/python/dist/clean/Lib/test/test_bsddb.py",
line 55, in assertSetEquals
    self.assertEqual(Set(seqn1), Set(seqn2))
AssertionError: Set([('e', 'Rossum'), ('r',
'invented'), ('t', 'Python'), ('w', 'van'), ('q',
'Guido'), ('y', None)]) != Set([('e', 'Rossum'), ('r',
'invented'), ('t', 'Python'), ('w', 'van'), ('q',
'Guido'), ('y', '')])
msg26638 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2005-10-20 05:17 
Logged In: YES 
user_id=33168

test_bsddb3 core dumps for me.  backtrace attached.

Do we really support 3.2 anymore?  Maybe we shouldn't?  I'm
on a gentoo system.  I don't know wha
msg26639 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2005-10-20 05:20 
Logged In: YES 
user_id=33168

Oops, that last comment got cut off.  I've got db-3.2 and
db-4.1 on my system at least.  Not sure why the older one is
picked up rather than the newer one.
msg26640 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2006-04-12 19:21 
Logged In: YES 
user_id=413

i'd prefer to just not support 3.2 anymore.

mind if i just change setup.py to not accept 3.2?
msg26641 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2006-04-13 03:20 
Logged In: YES 
user_id=33168

I don't mind and think it's reasonable to set whatever
minimum version for 2.5.  I don't think 3.2 support should
be removed from 2.4 though.  In 2.4, you can print a message
in setup.py if the version is too old.

I think that's conservative enough and reasonble.
msg26642 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2006-04-13 19:20 
Logged In: YES 
user_id=413

ok i've raised the minimum to 3.3 in python 2.5 trunk.  svn
r45368.
History
Date User Action Args
2022-04-11 14:56:13adminsetgithub: 42504
2005-10-20 04:41:03nnorwitzcreate