[issue25601] test_cpickle failure on the ware-gentoo-x86 buildbot

2015-12-01 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pytho

[issue25601] test_cpickle failure on the ware-gentoo-x86 buildbot

2015-12-01 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: I'm duping this one to issue25698 because while it came later, it has a lot more information. They are clearly the same bug. -- nosy: +barry superseder: -> The copy_reg module becomes unexpectedly empty in test_cpickle __

[issue25601] test_cpickle failure on the ware-gentoo-x86 buildbot

2015-11-13 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Could you reproduce the failure by running tests with the same seed on these machines? -- ___ Python tracker ___

[issue25601] test_cpickle failure on the ware-gentoo-x86 buildbot

2015-11-11 Thread Zachary Ware
Zachary Ware added the comment: 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. -- ___ Python tracker

[issue25601] test_cpickle failure on the ware-gentoo-x86 buildbot

2015-11-11 Thread Zachary Ware
Zachary Ware added the comment: 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. -- ___ Python tracker

[issue25601] test_cpickle failure on the ware-gentoo-x86 buildbot

2015-11-11 Thread Zachary Ware
Zachary Ware added the comment: 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. -- ___ Python tracker

[issue25601] test_cpickle failure on the ware-gentoo-x86 buildbot

2015-11-11 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- title: test_cpickle failure on the ware-gentoo-x86 builbot -> test_cpickle failure on the ware-gentoo-x86 buildbot ___ Python tracker ___ __