On Tue, Mar 12, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
[1]Still Failing - zopetoolkit_trunk - Build # 199
Error: Picked: zope.security = 4.0.0b1
[2]winbot / z3c.contents_py_265_32
[3]winbot / z3c.form_py_265_32
[4]winbot / z3c.formui_py_265_32
[5]winbot /
On Monday, March 11, 2013 10:33:30 PM Tres Seaver wrote:
Yep, saw that. There are some uncovered lines for which I have to add
tests left. Also, I just noticed while prorting zope.publisher to PyPy
that proxies cannot be adapted, which is a big issue for any view
libraries.
Ouch. That
On Tue, Mar 12, 2013 at 8:30 AM, Stephan Richter
stephan.rich...@gmail.com wrote:
On Monday, March 11, 2013 10:33:30 PM Tres Seaver wrote:
Yep, saw that. There are some uncovered lines for which I have to add
tests left. Also, I just noticed while prorting zope.publisher to PyPy
that
On Tuesday, March 12, 2013 09:14:26 AM Jim Fulton wrote:
Sorry, why do you want to adapt proxies? The lying about class,
which is arguably not lying, is intentional and facilitates adapting proxied
objects.
No, we really want to adapt the wrapped object, but that is currently not
working
On Tue, Mar 12, 2013 at 08:35:46AM -0400, Stephan Richter wrote:
On Monday, March 11, 2013 10:09:51 PM Tres Seaver wrote:
Also, is somebody running / reporting tests via
Travis? Where are those results going?
They should be running for all packages. I have turned off any notifications
On Tuesday, March 12, 2013 04:41:23 PM Marius Gedminas wrote:
Note: I think most packages pass fine under Travis, but some are failing
for some obscure reasons.
An overview would be good.
I could add a Travis column to http://zope3.pov.lt/py3/, I suppose. The
image URLs are trivial to
This is the summary for test reports received on the
zope-tests list between 2013-03-11 00:00:00 UTC and 2013-03-12 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:
