Issue 25601: test_cpickle failure on the ware-gentoo-x86 buildbot (original) (raw)

Created on 2015-11-11 08:31 by serhiy.storchaka, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (6)
msg254483 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2015-11-11 08:31
http://buildbot.python.org/all/builders/x86%20Gentoo%20Non-Debug%20with%20X%202.7/builds/100/steps/test/logs/stdio There are a lot of failures, all look as: ====================================================================== ERROR: test_simple_newobj (test.test_cpickle.FileIOCPicklerFastTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/buildbot/buildarea/2.7.ware-gentoo-x86/build/Lib/test/pickletester.py", line 1145, in test_simple_newobj s = self.dumps(x, proto) File "/buildbot/buildarea/2.7.ware-gentoo-x86/build/Lib/test/test_cpickle.py", line 141, in dumps p.dump(arg) AttributeError: 'module' object has no attribute '_reduce_ex' ---------------------------------------------------------------------- It looks as the _reduce_ex() function is missed in the copy_reg module. Have no ideas how it is possible.
msg254490 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2015-11-11 16:38
I also have no idea how that happened, but seems to have been a fluke. Build 101 is fine, and nothing has changed on that box.
msg254492 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2015-11-11 16:52
This also happened on my Windows buildbot: http://buildbot.python.org/all/builders/AMD64%20Windows8.1%20Non-Debug%202.7/builds/195 That build is running again as build 196.
msg254494 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2015-11-11 17:15
Build 196 on the Windows bot is fine. Could be a bizarre test ordering issue? Nothing else should have changed between builds 195 and 196 on the Windows bot.
msg254601 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2015-11-13 12:00
Could you reproduce the failure by running tests with the same seed on these machines?
msg255659 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2015-12-01 16:36
I'm duping this one to because while it came later, it has a lot more information. They are clearly the same bug.
History
Date User Action Args
2022-04-11 14:58:23 admin set github: 69787
2015-12-01 16:38:42 serhiy.storchaka set status: open -> closedresolution: duplicatestage: resolved
2015-12-01 16:36:48 barry set superseder: The copy_reg module becomes unexpectedly empty in test_cpicklemessages: + nosy: + barry
2015-11-13 12:00:11 serhiy.storchaka set messages: +
2015-11-11 17:15:26 zach.ware set messages: +
2015-11-11 16:52:16 zach.ware set messages: +
2015-11-11 16:38:53 zach.ware set messages: +
2015-11-11 15:38:33 serhiy.storchaka set title: test_cpickle failure on the ware-gentoo-x86 builbot -> test_cpickle failure on the ware-gentoo-x86 buildbot
2015-11-11 08:35:19 serhiy.storchaka set nosy: + pitrou, alexandre.vassalotti
2015-11-11 08:35:04 serhiy.storchaka set type: behaviorcomponents: + Testsversions: + Python 2.7
2015-11-11 08:31:35 serhiy.storchaka create