On Wed, Mar 20, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
> [1]Still Failing - zopetoolkit_trunk - Build # 207
Same four persistent import errors.
Back in February I thought these were caused by an incorrect setup.py in
ZODB. That's been fixed, yet the errors persist. And I can
This is the summary for test reports received on the
zope-tests list between 2013-03-18 00:00:00 UTC and 2013-03-19 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 03/19/2013 01:48 PM, Stephan Richter wrote:
> On Tuesday, March 19, 2013 08:38:23 AM GitHub wrote:
>> Commit: b2ae9a9bd5e3dc214f13c6ae77fa06ad55102aba
>> https://github.com/zopefoundation/zope.container/commit/b2ae9a9bd5e3dc
>>
>>
214f13c6ae77fa06
On 03/19/2013 07:36 PM, Brian Sutherland wrote:
Further things to do: make some performance improvements, try some
>real-world tests and release a alpha version.
I tried it against my app with good results so far:)
I did notice two regression and pushed failing tests to you py3 branch.
It seeme
On Tuesday, March 19, 2013 08:38:23 AM GitHub wrote:
> Commit: b2ae9a9bd5e3dc214f13c6ae77fa06ad55102aba
> https://github.com/zopefoundation/zope.container/commit/b2ae9a9bd5e3dc
> 214f13c6ae77fa06ad55102aba Author: Matthew Wilkes
> Date: 2013-03-19 (Tue, 19 Mar 2013)
>
> Changed path
On Tue, Mar 19, 2013 at 04:40:02PM +0200, Andrey Lebedev wrote:
> On 03/04/2013 08:40 PM, Andrey Lebedev wrote:
> >
> >As you may already know, there is an effort to port zope packages to
> >Python 3 going on. As part of this effort we want to port zope.testbrowser.
>
> Status update: test suite p
On 03/04/2013 08:40 PM, Andrey Lebedev wrote:
As you may already know, there is an effort to port zope packages to
Python 3 going on. As part of this effort we want to port zope.testbrowser.
Status update: test suite passes on webtest backend under python-2.6,
2.7 and 3.3.
Further things to
