➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

作者 neologix
收信人 asksol, jnoller, neologix, pitrou, vstinner
日期 2011-04-06.20:11:35
SpamBayes Score 5.956889e-05
Marked as misclassified 否
Message-id <1302120695.97.0.296723787225.issue11766@psf.upfronthosting.co.za>
In-reply-to
内容
Does this only happen on Cygwin buildbots ?
If yes, then it might simply be an issue with Cygwin's fork implementation, which is much slower than natively.
Right now, the test waits 0.5s before checking that the processes are started, after repopulating the pool. While 0.5s is normally way enough for forking a couple processes, it seems that under Cygwin this can take a surprising amount of time, see http://old.nabble.com/Slow-fork-issue---Win-x64-td19538601.html and also http://superuser.com/questions/133313/can-i-speed-up-cygwins-fork
Unless I misunderstand their benchmarks, the fork (+exec) rate of "date" from a shell can be as low as 5/sec, so I can only guess what forking cpython would take.
Maybe we could try to increase the timeout before checking the PIDs:

+    countdown = 10
-    countdown = 10
    while countdown and not all(w.is_alive() for w in p._pool):
        countdown -= 1
        time.sleep(DELTA)
历史
日期 用户 动作 参数
2011-04-06 20:11:36neologix修改recipients: + neologix, pitrou, vstinner, jnoller, asksol
2011-04-06 20:11:35neologix修改messageid: <1302120695.97.0.296723787225.issue11766@psf.upfronthosting.co.za>
2011-04-06 20:11:35neologix链接issue11766 messages
2011-04-06 20:11:35neologix创建