Le 14/11/2011 01:52, Christophe Combelles a écrit :
Le 13/11/2011 14:22, Tres Seaver a écrit :
[1] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-November/052554.html
This is the same hour-long timeout as yesterday in the buildout step:
mr.developer: Updated 'zope.viewlet' with subversion.
command timed out: 3600 seconds without output, killing pid 22071 process killed by signal 9 program finished with exit code -1 elapsedTime=4054.018485
I have no idea what is failing.
[2] FAILED Zope 3.4 KGS / Python2.4.6 64bit linux https://mail.zope.org/pipermail/zope-tests/2011-November/052563.html
[3] FAILED Zope 3.4 KGS / Python2.5.5 64bit linux https://mail.zope.org/pipermail/zope-tests/2011-November/052564.html
[4] FAILED Zope 3.4 Known Good Set / py2.4-32bit-linux https://mail.zope.org/pipermail/zope-tests/2011-November/052550.html
[5] FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux https://mail.zope.org/pipermail/zope-tests/2011-November/052548.html
[6] FAILED Zope 3.4 Known Good Set / py2.5-32bit-linux https://mail.zope.org/pipermail/zope-tests/2011-November/052559.html
[7] FAILED Zope 3.4 Known Good Set / py2.5-64bit-linux https://mail.zope.org/pipermail/zope-tests/2011-November/052552.html
If somebody who cares about the KGS could look at these failures and figure out why knew versions are slipping into the mix, that would be great. Otherwise, we should just quit testing it.
The initial build process of the kgs has no versions pinned, so it was being built with some of the latests libs that fail under python2.4. I have added versions in the toplevel buildout.cfg so that it shouldn't fail again.
I don't know if someone is interested but we have enough minor versions upgrade available to be able to release a maintenance versions of the KGS: 3.4.2
fixed http://buildbot.afpy.org/kgs3.4/builders/Python2.4.6%2064bit%20linux/builds/...
[8] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-November/052551.html
Stephan said yesterday he thought this was a chameleon bug. I just tried to reproduce this on a Linux box with a fresh checkout, using Python 2.5.5. The tests don't even run for me::
Traceback (most recent call last): File "/tmp/zft/bin/test", line 26, in<module> '--test-path', '/tmp/zft/src', File "/tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/__init__.py", line 30, in run failed = run_internal(defaults, args, script_parts=script_parts) File "/tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/__init__.py", line 41, in run_internal from zope.testrunner.runner import Runner File "/tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/runner.py", line 46, in<module> import zope.testrunner.tb_format File "/tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/tb_format.py", line 19, in<module> import zope.exceptions.exceptionformatter File "/tmp/zft/eggs/zope.exceptions-3.6.1-py2.5.egg/zope/exceptions/__init__.py", line 24, in<module> import zope.security File "/tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/__init__.py", line 17, in<module> from zope.security.management import checkPermission File "/tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/management.py", line 20, in<module> from zope.security import interfaces File "/tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/interfaces.py", line 19, in<module> from zope.schema import Text, TextLine File "/tmp/zft/eggs/zope.schema-4.0.0-py2.5.egg/zope/schema/__init__.py", line 16, in<module> from zope.schema._field import Field, Container, Iterable, Orderable File "/tmp/zft/eggs/zope.schema-4.0.0-py2.5.egg/zope/schema/_field.py", line 78 class SourceText(Text): ^ SyntaxError: invalid syntax
Tres.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )