Am 08.12.2011 um 02:00 schrieb Zope tests summarizer:
[...]
> [1]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit
> https://mail.zope.org/pipermail/zope-tests/2011-December/053761.html
> [2]FAILED Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64
> https://mail.zope.org/pipermail/zo
Could someone copy the existing zc.buildout-2.0.0a1-py3.2.egg file over
to zc.buildout-2.0.0a1-py3.3.egg on PyPI so it gets shlepped down when
we try to use the Python trunk against existing buildouts?
- C
___
Zope-Dev maillist - Zope-Dev@zope.org
ht
This is the summary for test reports received on the
zope-tests list between 2011-12-06 00:00:00 UTC and 2011-12-07 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:
http://docs.zope.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2011 02:36 AM, Michael Howitz wrote:
> Am 07.12.2011 um 02:00 schrieb Zope tests summarizer: [...]
>> Non-OK results --
>>
>> [1]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit
>> https://mail.zope.org/pipermail/zope-tests/2011-