Re: zope-tests - FAILED: 13, OK: 16, UNKNOWN: 2

On Fri, Feb 22, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
> [1]    FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux
> [2]    FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux

Same old (menu actions are now unicode).

> [3]    Still Failing - zopetoolkit_trunk - Build # 180
> [4]    Still Failing - zopetoolkit_trunk_app - Build # 162

New failure:

    Error: Picked: zope.publisher = 4.0.0a1

> [5]    winbot / z3c.authenticator_py_265_32

New failure:

    File "c:\buildslave\z3c.authenticator\build\src\z3c\authenticator\README.txt", line 140, in README.txt
    Failed example:
        p.password
    Expected:
        u'secret'
    Got:
        'secret'

> [6]    winbot / z3c.contents_py_265_32
> [7]    winbot / z3c.layer.ready2go_py_265_32

Same old (<form> attribute ordering differences).

> [8]    winbot / z3c.recipe.paster_py_265_32

New failure during doctest setup:

    Traceback (most recent call last):
      File "c:\Python26_32\lib\unittest.py", line 270, in run
        self.setUp()
      File "c:\Python26_32\lib\doctest.py", line 2131, in setUp
        self._dt_setUp(test)
      File "c:\buildslave\z3c.recipe.paster\build\src\z3c\recipe\paster\tests.py", line 27, in setUp
        zc.buildout.testing.install('RestrictedPython', test)
      File "c:\eggs\zc.buildout-1.7.1-py2.6.egg\zc\buildout\testing.py", line 605, in install
        if dist.location.endswith('.egg'):
    AttributeError: 'NoneType' object has no attribute 'location'

> [9]    winbot / z3c.tabular_py_265_32

Same old (<form> attribute ordering differences).

> [10]   winbot / zope.app.dependable_py_265_32

New failure:

    The constraint, 4.0.3, is not consistent with the requirement,
    'zope.interface>=4.0.4'.

> [11]   winbot / zope.app.wsgi_py_265_32

New failure due to extra unicode prefixes in unexpected places:

    File "c:\buildslave\zope.app.wsgi\build\src\zope\app\wsgi\README.txt", line 108, in README.txt
    Failed example:
        pprint(environ)
    Expected:
        {'PATH_INFO': ...
         'REMOTE_USER': 'zope.anybody',
         'wsgi.input': ...
         'wsgi.logging_info': 'zope.anybody'}
    Got:
        {'PATH_INFO': ...
         'REMOTE_USER': u'zope.anybody',
         'wsgi.input': ...
         'wsgi.logging_info': u'zope.anybody'}

I suspect having unicode strings in the WSGI environ goes against
PEP-3333.  And looks like I'm right!

    "Also note that CGI-defined variables must be native strings, if
    they are present at all. It is a violation of this specification for
    any CGI variable's value to be of any type other than str."
        -- http://www.python.org/dev/peps/pep-3333/

REMOTE_USER is part of the CGI spec.

I've no idea about wsgi.logging_info, IIRC it's only used by Zope (a
failed attempt to introduce a new WSGI standard that didn't pan out, or
something like that).  I suspect it's better to be consistent here.

> [12]   winbot / zope.contenttype_py_265_32

Latest build is all green.

> [13]   winbot / zope.datetime_py_265_32

Moved to github, winbot looked in svn.  This will clear up after a
winbot reconfig.

> [14]   winbot / zope.site_py_265_32

Latest build is all green.

> [15]   winbot / ztk_10 py_254_win32

Interesting new failure in zope.dublincore:

    File "c:\eggs\zope.dublincore-3.7.0-py2.5.egg\zope\dublincore\tests\timeannotators.txt", line 53, in timeannotators.txt
    Failed example:
        content.created
    Expected:
        datetime.datetime(<DATETIME>, tzinfo=<UTC>)
    Got:
        datetime.datetime(2013, 2, 21, 20, 23, 32, tzinfo=<UTC>)

Marius Gedminas
-- 
http://pov.lt/ -- Zope 3/BlueBream consulting and development

_______________________________________________
Zope-Dev maillist  -  [email protected]
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 )

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iD8DBQFRJxB8kVdEXeem148RAnB8AJwLj22kmbw2d0TgaAF+rV7vx+RHewCdFj4b
yyaKyoleh/oV/IMfkeGJNa0=
=Gb0d
-----END PGP SIGNATURE-----