This is the summary for test reports received on the zope-tests list between 2017-05-06 00:00:00 UTC and 2017-05-07 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 ---------------- [1] winbot / z3c.contents_py_270_win32 [2] winbot / z3c.contents_py_270_win64 [3] winbot / z3c.coverage_py_270_win32 [4] winbot / z3c.coverage_py_270_win64 [5] winbot / z3c.jsonrpc_py_270_win32 [6] winbot / z3c.jsonrpc_py_270_win64 [7] winbot / z3c.ptcompat_py_270_win32 [8] winbot / z3c.ptcompat_py_270_win64 [9] winbot / z3c.testing_py_270_win32 [10] winbot / z3c.testing_py_270_win64 [11] winbot / zc.catalog_py_270_win64 [12] winbot / zc.resourcelibrary_py_270_win32 [13] winbot / zc.resourcelibrary_py_270_win64 [14] winbot / zope.app.authentication_py_270_win32 [15] winbot / zope.app.authentication_py_270_win64 [16] winbot / zope.app.exception_py_270_win32 [17] winbot / zope.app.exception_py_270_win64 [18] winbot / zope.app.localpermission_py_270_win32 [19] winbot / zope.app.localpermission_py_270_win64 [20] winbot / zope.app.testing_py_270_win32 [21] winbot / ztk_dev py_270_win32 [22] winbot / ztk_dev py_270_win64 [23] winbot / ztk_dev py_330_win32 [24] winbot / ztk_dev py_330_win64 Non-OK results -------------- [1] FAILED winbot / z3c.contents_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105094.html [2] FAILED winbot / z3c.contents_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105098.html [3] FAILED winbot / z3c.coverage_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105089.html [4] FAILED winbot / z3c.coverage_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105087.html [5] FAILED winbot / z3c.jsonrpc_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105100.html [6] FAILED winbot / z3c.jsonrpc_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105093.html [7] FAILED winbot / z3c.ptcompat_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105084.html [8] FAILED winbot / z3c.ptcompat_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105096.html [9] FAILED winbot / z3c.testing_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105095.html [10] FAILED winbot / z3c.testing_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105086.html [11] FAILED winbot / zc.catalog_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105088.html [12] FAILED winbot / zc.resourcelibrary_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105091.html [13] FAILED winbot / zc.resourcelibrary_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105085.html [14] FAILED winbot / zope.app.authentication_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105097.html [15] FAILED winbot / zope.app.authentication_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105090.html [16] FAILED winbot / zope.app.exception_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105092.html [17] FAILED winbot / zope.app.exception_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105083.html [18] FAILED winbot / zope.app.localpermission_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105082.html [19] FAILED winbot / zope.app.localpermission_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105081.html [20] FAILED winbot / zope.app.testing_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105099.html [21] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105101.html [22] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105102.html [23] FAILED winbot / ztk_dev py_330_win32 https://mail.zope.org/pipermail/zope-tests/2017-May/105103.html [24] FAILED winbot / ztk_dev py_330_win64 https://mail.zope.org/pipermail/zope-tests/2017-May/105104.html
Am 08.05.2017 um 01:00 schrieb Zope tests summarizer <noreply@zope.org>:
This is the summary for test reports received on the zope-tests list between 2017-05-06 00:00:00 UTC and 2017-05-07 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
Who runs and maintains the service producing these mails? (The header says that they are set by a host named hetzner04.zopefoundation.org.) Context: On the Zope 2 Resurrection Sprint we had the idea it could be used to collect mails from Travis-CI, too. As Travis-CI has now a cron feature and the tests of some packages are already run there on a weekly basis. I’d volunteer to update the processing script to be able to process Travis-CI mails, too. -- Mit freundlichen Grüßen Michael Howitz
On Mon, May 8, 2017, at 11:36, Michael Howitz wrote:
Who runs and maintains the service producing these mails? (The header says that they are set by a host named hetzner04.zopefoundation.org.)
Apparently this is the same as download.zope.org, to which Tres, Jim, Marius and me still have root access. The "zope" user on that machine has a crontab entry for running the test summarizer, installed locally at /home/zope/z3c.testsummarizer The code for this used to be at svn://svn.zope.org/repos/main/z3c.testsummarizer/trunk - and probably wasn't migrated to github.
I’d volunteer to update the processing script to be able to process Travis-CI mails, too.
If you or someone else can remind me how to create a new user under Debian, I'll get you a user account on that box, so you have a look. Hanno
I really hate to see any more work done on this machine. Activity on it is ad hoc. It's more or less a bone yard at this point. Jim On Mon, May 8, 2017 at 8:59 AM, Hanno Schlichting <hanno@hannosch.eu> wrote:
On Mon, May 8, 2017, at 11:36, Michael Howitz wrote:
Who runs and maintains the service producing these mails? (The header says that they are set by a host named hetzner04.zopefoundation.org.)
Apparently this is the same as download.zope.org, to which Tres, Jim, Marius and me still have root access.
The "zope" user on that machine has a crontab entry for running the test summarizer, installed locally at /home/zope/z3c.testsummarizer
The code for this used to be at svn://svn.zope.org/repos/main/z3c.testsummarizer/trunk - and probably wasn't migrated to github.
I’d volunteer to update the processing script to be able to process Travis-CI mails, too.
If you or someone else can remind me how to create a new user under Debian, I'll get you a user account on that box, so you have a look.
Hanno _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org 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 )
-- Jim Fulton http://jimfulton.info
Am 08.05.2017 um 15:50 schrieb Jim Fulton <jim@jimfulton.info>:
I really hate to see any more work done on this machine. Activity on it is ad hoc. It's more or less a bone yard at this point.
Okay. But could you import
svn://svn.zope.org/repos/main/z3c.testsummarizer
into GitHub, so it can be run later on a different infrastructure? (Maybe as private project if it contains sensitive data.) -- Mit freundlichen Grüßen Michael Howitz
On Wed, May 10, 2017 at 11:18 AM, Michael Howitz <icemac@gmx.net> wrote:
Am 08.05.2017 um 15:50 schrieb Jim Fulton <jim@jimfulton.info>:
I really hate to see any more work done on this machine. Activity on it is ad hoc. It's more or less a bone yard at this point.
Okay. But could you import
svn://svn.zope.org/repos/main/z3c.testsummarizer
into GitHub, so it can be run later on a different infrastructure? (Maybe as private project if it contains sensitive data.)
Yup. Jim -- Jim Fulton http://jimfulton.info
On Wed, May 10, 2017 at 11:25 AM, Jim Fulton <jim@jimfulton.info> wrote:
On Wed, May 10, 2017 at 11:18 AM, Michael Howitz <icemac@gmx.net> wrote:
Am 08.05.2017 um 15:50 schrieb Jim Fulton <jim@jimfulton.info>:
I really hate to see any more work done on this machine. Activity on it is ad hoc. It's more or less a bone yard at this point.
Okay. But could you import
svn://svn.zope.org/repos/main/z3c.testsummarizer
into GitHub, so it can be run later on a different infrastructure? (Maybe as private project if it contains sensitive data.)
Yup.
https://github.com/zopefoundation/z3c.testsummarizer Jim -- Jim Fulton http://jimfulton.info
Am 10.05.2017 um 17:39 schrieb Jim Fulton <jim@jimfulton.info>: […]
Thank you! -- Mit freundlichen Grüßen Michael Howitz
I made one more change to the test summarizer and disabled the CMF test summary. As far as I can tell the cmf-tests list is silent since 2013 and we only get an empty "spam" summary to zope-cmf (https://mail.zope.org/pipermail/zope-cmf/2017-May/date.html#start) each day. Those should stop coming now. To test the change, I've invoked the script once manually, resulting in the extra mail for Zope tests today. Hanno
participants (4)
-
Hanno Schlichting -
Jim Fulton -
Michael Howitz -
Zope tests summarizer