Hi,
zc.async's shutdown mechanism doesn't really work with Zope 2's SIGTERM
handling: in my case it causes the Async's threaded dispatcher to die in
the middle of something:
Exception in thread Thread-1 (most likely raised during interpreter
shutdown):
Traceback (most recent call last):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/29/2012 08:00 PM, Zope tests summarizer wrote:
This is the summary for test reports received on the zope-tests list
between 2012-02-28 00:00:00 UTC and 2012-02-29 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
Hi,
Did you look how http://pypi.python.org/pypi/plone.app.async have done the
integration with Zope2?
Vincent Fretin
Ecreall
Site : http://vincentfretin.ecreall.com
On Thu, Mar 1, 2012 at 12:19 PM, Christian Theune c...@gocept.com wrote:
Hi,
zc.async's shutdown mechanism doesn't really
On Thu, Mar 1, 2012 at 1:42 PM, Vincent Fretin vincent.fre...@gmail.com wrote:
Did you look how http://pypi.python.org/pypi/plone.app.async have done the
integration with Zope2?
IIRC we (Jarn) ran into the same problem when running p.a.async. Our
solution was to switch to using SIGINT for
This is the summary for test reports received on the
zope-tests list between 2012-02-29 00:00:00 UTC and 2012-03-01 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[1]UNKNOWN UNKNOWN : winbot / ztk_11 py_265_win64
https://mail.zope.org/pipermail/zope-tests/2012-March/058792.html
[2]UNKNOWN UNKNOWN : winbot / ztk_11 py_265_win64
https://mail.zope.org/pipermail/zope-tests/2012-March/058767.html
Hello,
Restarted winbot, let's see what happens...
On Thu, 01 Mar 2012 21:32:55 -0500 you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[1]UNKNOWN UNKNOWN : winbot / ztk_11 py_265_win64
https://mail.zope.org/pipermail/zope-tests/2012-March/058792.html
[2]UNKNOWN UNKNOWN :
