[Zope-dev] zope-tests - FAILED: 10, OK: 12

[Marius Gedminas]

On Tue, Mar 12, 2013 at 10:30:33AM +0200, Marius Gedminas wrote:
> On Tue, Mar 12, 2013 at 01:00:02AM +0000, 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 / z3c.layer.ready2go_py_265_32
> > [7]    winbot / z3c.pagelet_py_265_32
> 
> lxml
> 
> Fix for this is in progress AFAIU.  Last I heard Adam was waiting for
> some Rackspace credentials so he can make a backup of the winbot VM
> before messing with compilers.
> 
> > [6]    winbot / z3c.menu.ready2go_py_265_32
> 
> Moved to github; zope.winbot fix pushed
> 
> > [8]    winbot / zope.app.authentication_py_265_32
> 
> Unicode principal names
> 
> > [9]    winbot / zope.app.http_py_265_32
> 
> AttributeError: 'NoneType' object has no attribute 'group'
> 
> inside zc.buildout-1.7.1-py2.6.egg\zc\buildout\easy_install.py
> 
> I've a sense of deja vu about this, but I don't remember if I got to the
> root of the problem when I saw it first.

Oh, right, that's what zc.buildout 1.7 does when it encounters a
zc.buildout 2.0-only feature

  [versions]
  zope.app.wsgi = <4.0dev

I'll ask Adam to make winbot use each package's bundled bootstrap.py
instead of using a shared common zc.builout-1.7-only bootstrap.

This will mean a bunch of failures due to stale bootstrap.py files, but
I'm sure we can deal with that easily enough.

Marius Gedminas
-- 
http://pov.lt/ -- Zope 3/BlueBream consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://mail.zope.org/pipermail/zope-dev/attachments/20130312/f5307bba/attachment.sig>