Guido van Rossum added the comment: Was this always so or did it recently start? Victor has made a ton of changes.
Anyway, I imagine there may be some objects stuck in cycles and the collection may not happen until a random later time, and the tests do timing-specific stuff so the number of objects created and deleted varies per run. Perhaps adding some well-aimed gc.collect() calls to some tearDown() methods would make this go away? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22104> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
