Message224284
| Author |
gvanrossum |
| Recipients |
giampaolo.rodola, gvanrossum, pitrou, vstinner, yselivanov |
| Date |
2014年07月30日.01:41:49 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1406684509.79.0.134123549645.issue22104@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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? |
|