[issue5073] bsddb/test/test_lock.py sometimes fails due to floating point error

Jesús Cea Avión added the comment: Patch up-ported to pybsddb 4.8.4. -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailin

[issue5073] bsddb/test/test_lock.py sometimes fails due to floating point error

Mark Dickinson added the comment: Fixed in r68978 (trunk) and r68979 (2.6). bsddb is no longer part of the standard Python distribution for 3.x, so the patch doesn't apply there. Thank you! -- resolution: accepted -> fixed status: open -> closed _

[issue5073] bsddb/test/test_lock.py sometimes fails due to floating point error

Hirokazu Yamamoto added the comment: Could you commit please? :-) ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue5073] bsddb/test/test_lock.py sometimes fails due to floating point error

Mark Dickinson added the comment: Looks good to me! If it were me I'd probably just code the test directly as self.assertTrue((end_time-start_time) >= 0.0999) to avoid having to look for epsilon when reading. Do you want to commit it or shall I? -- nosy: +marketdickinson resolutio

[issue5073] bsddb/test/test_lock.py sometimes fails due to floating point error

New submission from Hirokazu Yamamoto : time.time() returns floating point, so sometimes folloing assertion in LockingTestCase#test03_lock_timeout fails due to floating point calculation error. >self.assertTrue((end_time-start_time) >= 0.1 end_time-start_time becomes 0.099046326 for insta