Issue 10402: sporadic test_bsddb3 failures (original) (raw)
Issue10402
Created on 2010-11-13 00:51 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (4) | ||
|---|---|---|
| msg121100 - (view) | Author: Antoine Pitrou (pitrou) *  |
Date: 2010-11-13 00:51 |
| test_bsddb3 often produces the following failure under the Windows buildbots. It could probably be solved by choosing a larger timeout (time.time() on Windows is rather imprecise): test test_bsddb3 failed -- Traceback (most recent call last): File "D:\cygwin\home\db3l\buildarea\2.7.bolen-windows7\build\lib\bsddb\test\test_lock.py", line 139, in test04_lock_timeout2 self.assertTrue((end_time-start_time) >= 0.0999) AssertionError: False is not True | ||
| msg122331 - (view) | Author: Hirokazu Yamamoto (ocean-city) * |
Date: 2010-11-25 05:10 |
| This should be duplicate of #3892. I suppose timeout in this test might be very short. Refers to http://www.systomath.eu/doc/BerkeleyDb-4.7/html/api_c/rep_timeout.html timeout is in microseconds, so self.dbenvMaster.rep_set_timeout(db.DB_REP_CONNECTION_RETRY,100123) means only 100 milliseconds. (I don't know BSDDB entirely, so maybe this might be valid value though) | ||
| msg221709 - (view) | Author: Mark Lawrence (BreamoreBoy) * | Date: 2014-06-27 18:57 |
| As #3892 has been closed this can also be closed. | ||
| msg221788 - (view) | Author: Jesús Cea Avión (jcea) * |
Date: 2014-06-28 14:03 |
| Closed as requested. |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:08 | admin | set | github: 54611 |
| 2014-06-28 14:03:10 | jcea | set | status: open -> closedresolution: out of datemessages: + stage: needs patch -> resolved |
| 2014-06-27 18:57:47 | BreamoreBoy | set | nosy: + BreamoreBoymessages: + |
| 2010-11-25 05:10:39 | ocean-city | set | nosy: + ocean-citymessages: + |
| 2010-11-13 00:51:35 | pitrou | create |