Re: zope-tests - FAILED: 28, OK: 35, UNKNOWN: 2
Patrick Gerken <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <CAFefbnHBJMQPZoq+n+7rm+e7rCh1jxvGQXskkQFLaXuyJUjnUg@mail.gmail.com> |
All failures are because of import errors for zope.interface. Looking at some newer builds, the new failure is that pkg_resources are missing. Something seems to be seriously screwed up there. The two unknown build status are due to a timeout while trying to kill a process. I wish these builds would happen with Jenkins. With the right permission one can even see TTW whats in the working directory. On Sat, May 5, 2012 at 3:00 AM, Zope tests summarizer <[email protected]> wrote: > This is the summary for test reports received on the > zope-tests list between 2012-05-03 00:00:00 UTC and 2012-05-04 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/zopetoolkit/process/buildbots.html#the-nightly-builds > > Reports received > ---------------- > > Bluebream / Python2.5.5 64bit linux > Bluebream / Python2.6.7 64bit linux > Bluebream / Python2.7.2 64bit linux > [1] UNKNOWN : winbot / ztk_dev py_265_win32 > [2] UNKNOWN : winbot / ztk_dev py_265_win64 > ZTK 1.0dev / Python2.4.6 Linux 64bit > ZTK 1.0dev / Python2.5.5 Linux 64bit > ZTK 1.0dev / Python2.6.7 Linux 64bit > ZTK 1.1 / Python2.5.5 Linux 64bit > ZTK 1.1 / Python2.6.7 Linux 64bit > ZTK 1.1 / Python2.7.2 Linux 64bit > ZTK 1.1dev / Python2.5.5 Linux 64bit > ZTK 1.1dev / Python2.6.7 Linux 64bit > ZTK 1.1dev / Python2.7.2 Linux 64bit > Zope 3.4 Known Good Set / py2.4-32bit-linux > Zope 3.4 Known Good Set / py2.4-64bit-linux > Zope 3.4 Known Good Set / py2.5-32bit-linux > Zope 3.4 Known Good Set / py2.5-64bit-linux > Zope-2.10 Python-2.4.6 : Linux > Zope-2.11 Python-2.4.6 : Linux > Zope-2.12 Python-2.6.6 : Linux > Zope-2.12-alltests Python-2.6.6 : Linux > Zope-2.13 Python-2.6.6 : Linux > Zope-2.13-alltests Python-2.6.6 : Linux > Zope-trunk Python-2.6.6 : Linux > Zope-trunk-alltests Python-2.6.6 : Linux > winbot / ZODB_dev py_265_win32 > [3] winbot / zc.resourcelibrary_py_265_32 > [4] winbot / zc.table_py_265_32 > [5] winbot / zope.app.appsetup_py_265_32 > [6] winbot / zope.app.authentication_py_265_32 > [7] winbot / zope.app.broken_py_265_32 > [8] winbot / zope.app.dependable_py_265_32 > [9] winbot / zope.app.interface_py_265_32 > [10] winbot / zope.app.locales_py_265_32 > [11] winbot / zope.app.localpermission_py_265_32 > [12] winbot / zope.app.publisher_py_265_32 > [13] winbot / zope.app.schema_py_265_32 > [14] winbot / zope.app.session_py_265_32 > [15] winbot / zope.app.wsgi_py_265_32 > [16] winbot / zope.browsermenu_py_265_32 > [17] winbot / zope.contenttype_py_265_32 > [18] winbot / zope.datetime_py_265_32 > [19] winbot / zope.event_py_265_32 > [20] winbot / zope.interface_py_265_32 > [21] winbot / zope.location_py_265_32 > [22] winbot / zope.location_py_265_32 > [23] winbot / zope.location_py_265_32 > [24] winbot / zope.principalregistry_py_265_32 > [25] winbot / zope.processlifetime_py_265_32 > [26] winbot / zope.publisher_py_265_32 > [27] winbot / zope.ramcache_py_265_32 > [28] winbot / zope.sendmail_py_265_32 > [29] winbot / zope.size_py_265_32 > [30] winbot / zope.traversing_py_265_32 > winbot / ztk_10 py_254_win32 > winbot / ztk_10 py_265_win32 > winbot / ztk_10 py_265_win64 > winbot / ztk_11 py_254_win32 > winbot / ztk_11 py_265_win32 > winbot / ztk_11 py_265_win64 > winbot / ztk_11 py_270_win32 > winbot / ztk_11 py_270_win64 > winbot / ztk_dev py_270_win32 > winbot / ztk_dev py_270_win64 > > Non-OK results > -------------- > > [1] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061607.html > > > [2] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win64 > https://mail.zope.org/pipermail/zope-tests/2012-May/061608.html > > > [3] FAILED winbot / zc.resourcelibrary_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061573.html > > > [4] FAILED winbot / zc.table_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061570.html > > > [5] FAILED winbot / zope.app.appsetup_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061564.html > > > [6] FAILED winbot / zope.app.authentication_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061582.html > > > [7] FAILED winbot / zope.app.broken_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061568.html > > > [8] FAILED winbot / zope.app.dependable_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061560.html > > > [9] FAILED winbot / zope.app.interface_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061579.html > > > [10] FAILED winbot / zope.app.locales_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061572.html > > > [11] FAILED winbot / zope.app.localpermission_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061563.html > > > [12] FAILED winbot / zope.app.publisher_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061574.html > > > [13] FAILED winbot / zope.app.schema_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061580.html > > > [14] FAILED winbot / zope.app.session_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061581.html > > > [15] FAILED winbot / zope.app.wsgi_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061565.html > > > [16] FAILED winbot / zope.browsermenu_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061571.html > > > [17] FAILED winbot / zope.contenttype_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061558.html > > > [18] FAILED winbot / zope.datetime_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061559.html > > > [19] FAILED winbot / zope.event_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061567.html > > > [20] FAILED winbot / zope.interface_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061566.html > > > [21] FAILED winbot / zope.location_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061606.html > > > [22] FAILED winbot / zope.location_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061604.html > > > [23] FAILED winbot / zope.location_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061583.html > > > [24] FAILED winbot / zope.principalregistry_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061578.html > > > [25] FAILED winbot / zope.processlifetime_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061576.html > > > [26] FAILED winbot / zope.publisher_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061569.html > > > [27] FAILED winbot / zope.ramcache_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061562.html > > > [28] FAILED winbot / zope.sendmail_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061561.html > > > [29] FAILED winbot / zope.size_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061577.html > > > [30] FAILED winbot / zope.traversing_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-May/061575.html > > > _______________________________________________ > 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 ) _______________________________________________ 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 )