Antoine Pitrou added the comment: > I do see a couple of failed assertions on Windows which presumably > happen in a child process because they do not cause a failure: > > Assertion failed: !collecting, file ..\Modules\gcmodule.c, line > 1617 > > The assertion is in _PyGC_CollectNoFail() and checks that it is not > called recursively. See > > > http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/2510/steps/test/logs/stdio
That's extremely weird. _PyGC_CollectNoFail() is only called from PyImport_Cleanup, which itself is only called from Py_Finalize() and Py_EndInterpreter(). It should be basically impossible for the GC to be already collecting garbage at that point... Perhaps you could try to find out in which test this happens? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8713> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
