Re: zope-tests - FAILED: 23, OK: 20

Marius Gedminas <[email protected]>
Newsgroups gmane.comp.web.zope.devel
Message-ID <20130219073202.GB1462@platonas>
TL;DR: three outstanding test failures where rendered HTML doesn't match
expectations:
  - z3c.contents
  - z3c.layer.ready2go
  - z3c.tabular

On Tue, Feb 19, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
> [1]    FAILED  Still Failing - zopetoolkit_trunk - Build # 177
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072575.html

Build # 178:

  IOError: [Errno 2] No such file or directory: '/home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.annotation/setup.py'

zope.annotation was moved to Github very recently.

> [4]    FAILED  winbot / z3c.configurator_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072571.html

Success in next build!

> [5]    FAILED  winbot / z3c.contents_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072597.html

Failure in next build:

  File "c:\buildslave\z3c.contents\build\src\z3c\contents\README.txt", line 111, in README.txt
  Failed example:
      print firstPage.render()
  Expected:
      (bunch of HTML)
  Got:
      (bunch of HTML)

What an unhelpful test failure output.  And +REPORT_NDIFF would not help,
because the HTML is formatted rather differently.  Some output normalization is
sorely needed here.

> [6]    FAILED  winbot / z3c.jsonrpc_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072558.html

Success in next build!

> [7]    FAILED  winbot / z3c.jsontree_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072556.html

Success in next build!

> [8]    FAILED  winbot / z3c.language.switch_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072569.html

Success in next build!

> [9]    FAILED  winbot / z3c.layer.ready2go_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072598.html

Failure in next build:

  File "c:\buildslave\z3c.layer.ready2go\build\src\z3c\layer\ready2go\README.txt", line 384, in README.txt
  Failed example:
      print addForm.render()
  Expected:
      (bunch of HTML)
  Got:
      (bunch of HTML)

> [10]   FAILED  winbot / z3c.menu.ready2go_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072559.html

Success in next build!

> [11]   FAILED  winbot / z3c.password_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072564.html

Success in next build!

> [12]   FAILED  winbot / z3c.table_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072560.html

Success in next build!

> [13]   FAILED  winbot / z3c.tabular_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072596.html

Failure in next build:

  File "c:\buildslave\z3c.tabular\build\src\z3c\tabular\README.txt", line 124, in README.txt
  Failed example:
      print contentSubFormTable.render()
  Expected:
      (bunch of HTML)
  Got:
      (bunch of HTML)

> [14]   FAILED  winbot / zc.sourcefactory_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072570.html

Success in next build!

> [15]   FAILED  winbot / zope.app.applicationcontrol_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072566.html

Success in next build!

> [16]   FAILED  winbot / zope.app.form_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072562.html

Success in next build!

> [17]   FAILED  winbot / zope.app.generations_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072557.html

Success in next build!

> [18]   FAILED  winbot / zope.app.renderer_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072565.html

Success in next build!

> [19]   FAILED  winbot / zope.app.rotterdam_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072572.html

Success in next build!

> [20]   FAILED  winbot / zope.app.security_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072561.html

Success in next build!

> [21]   FAILED  winbot / zope.app.server_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072563.html

Success in next build!

> [22]   FAILED  winbot / zope.formlib_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072568.html

Success in next build!

> [23]   FAILED  winbot / zope.security_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2013-February/072567.html

I pushed my workaround (with duplicate code extracted into a helper
called _fmt_address) just now.

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 )
signature.asc (application/pgp-signature, 190 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iD8DBQFRIypykVdEXeem148RAigoAJ46Bt1DVkVjpseczijsouOiYESArACdFta8
ISGFhIzycbNRPOtacBfhisY=
=/dDi
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.