Message195181
| Author |
pitrou |
| Recipients |
Stan.Seibert, asksol, brandon-rhodes, catalin.iacob, christian.heimes, dholth, gregory.p.smith, jnoller, mrmekon, ned.deily, neologix, numbernine, pitrou, python-dev, rcoyner, sbt, vsekhar |
| Date |
2013年08月14日.15:37:36 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1273793863.62351434.1376494648984.JavaMail.root@zimbra10-e2.priv.proxad.net> |
| In-reply-to |
<1376493157.04.0.429672297278.issue8713@psf.upfronthosting.co.za> |
| Content |
> 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? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年08月14日 15:37:36 | pitrou | set | recipients:
+ pitrou, gregory.p.smith, christian.heimes, ned.deily, jnoller, rcoyner, asksol, dholth, brandon-rhodes, neologix, catalin.iacob, python-dev, sbt, numbernine, vsekhar, mrmekon, Stan.Seibert |
| 2013年08月14日 15:37:36 | pitrou | link | issue8713 messages |
| 2013年08月14日 15:37:36 | pitrou | create |
|