This is the summary for test reports received on the zope-tests list between 2013-02-10 00:00:00 UTC and 2013-02-11 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 ---------------- Successful - zopetoolkit_trunk - Build # 169 Successful - zopetoolkit_trunk_app - Build # 152 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / zope.security_py_265_32 [2] winbot / zope.testrunner_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 [3] winbot / ztk_11 py_254_win32 [4] winbot / ztk_11 py_265_win32 [5] winbot / ztk_11 py_265_win64 [6] winbot / ztk_11 py_270_win32 [7] winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072239.html [2] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072240.html [3] FAILED winbot / ztk_11 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072230.html [4] FAILED winbot / ztk_11 py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072232.html [5] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072233.html [6] FAILED winbot / ztk_11 py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072231.html [7] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072234.html
On Tue, Feb 12, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
Non-OK results --------------
[1] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072239.html
Bootstrap failed: While: Initializing. Error: Couldn't open c:\buildslave\zope.security\build\buildout.cfg program finished with exit code 0 because zope.security lives on Github now. Fixed in zope.wineggbuilder r129311. Incidentally, why does bootstrap exit with 0 when it fails in winbot? I tried to reproduce that with wget http://downloads.buildout.org/1/bootstrap.py python bootstrap.py and wget http://downloads.buildout.org/2/bootstrap.py python bootstrap.py in an empty directory, and both modern bootstraps returned exit code 1.
[2] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072240.html
This was testing r129308 in svn, which has only a single MOVED_TO_GITHUB file. I've updated zope.wineggbuilder in r129305 to tell it to look for zope.testrunner on Github. Does zope.wineggbuilder update its configs automatically, or do I need to ping some admins when I make changes like that?
[3] FAILED winbot / ztk_11 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072230.html
Another bootstrap failure, this time with AttributeError: 'NoneType' object has no attribute 'location' which is the awkward way an old bootstrap.py script says "halp this bootstrap 2.0.0 thing I don't know what do" while falling over. I'd update the boostrap, if I could figure out where in svn is the thing called "ztk_1_1". Buildbot makes it unreasonably hard to figure this stuff out (this is why I publish the master.cfg of my buildbot at http://zope3.pov.lt/buildbot/. Speaking of which, it's red as a very red thing, but I haven't seen any failure emails! What's going on there?). I'm guessing this might be svn+ssh://svn.zope.org/repos/main/zopetoolkit/branches/1.1 Should be fixed in r129312.
[4] FAILED winbot / ztk_11 py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072232.html
[5] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072233.html
[6] FAILED winbot / ztk_11 py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072231.html
[7] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072234.html
Haven't checked, assuming the same bootstrap issue. It feels good to have CI. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On 02/12/2013 08:58 AM, Marius Gedminas wrote:
On Tue, Feb 12, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
Non-OK results --------------
[1] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072239.html
Bootstrap failed:
While: Initializing. Error: Couldn't open c:\buildslave\zope.security\build\buildout.cfg program finished with exit code 0
because zope.security lives on Github now.
Fixed in zope.wineggbuilder r129311.
Incidentally, why does bootstrap exit with 0 when it fails in winbot? I tried to reproduce that with
wget http://downloads.buildout.org/1/bootstrap.py python bootstrap.py
and
wget http://downloads.buildout.org/2/bootstrap.py python bootstrap.py
in an empty directory, and both modern bootstraps returned exit code 1.
Weird, because there's no wrapper around that bootstrapping...
[2] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072240.html
This was testing r129308 in svn, which has only a single MOVED_TO_GITHUB file.
I've updated zope.wineggbuilder in r129305 to tell it to look for zope.testrunner on Github.
Does zope.wineggbuilder update its configs automatically, or do I need to ping some admins when I make changes like that?
It's all manual, all that is read by master.cfg, buildbot is a windows service, yada yada... On top of that I would not be happy to auto update master.cfg ;-) I'm trying to watch for changes, feel free to kick me if I miss it.
[3] FAILED winbot / ztk_11 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072230.html
Another bootstrap failure, this time with
AttributeError: 'NoneType' object has no attribute 'location'
which is the awkward way an old bootstrap.py script says "halp this bootstrap 2.0.0 thing I don't know what do" while falling over.
I'd update the boostrap, if I could figure out where in svn is the thing called "ztk_1_1". Buildbot makes it unreasonably hard to figure this stuff out (this is why I publish the master.cfg of my buildbot at http://zope3.pov.lt/buildbot/.
svn://svn.zope.org/repos/main/zope.wineggbuilder/trunk/master.cfg at your service ;-) Just included that info on the root page. Speaking of which, it's red as a very
red thing, but I haven't seen any failure emails! What's going on there?).
I'm guessing this might be svn+ssh://svn.zope.org/repos/main/zopetoolkit/branches/1.1
It is, http://winbot.zope.org/builders/ztk_11%20py_254_win32/builds/699/steps/svn-i... tells you the URL
Should be fixed in r129312.
[4] FAILED winbot / ztk_11 py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072232.html
[5] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072233.html
[6] FAILED winbot / ztk_11 py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072231.html
[7] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072234.html
Haven't checked, assuming the same bootstrap issue.
It feels good to have CI.
Marius Gedminas
_______________________________________________ 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 )
-- Best regards, Adam GROSZER -- Quote of the day: To teach is to learn.
On Tue, Feb 12, 2013 at 09:15:22AM +0100, Adam GROSZER wrote:
On 02/12/2013 08:58 AM, Marius Gedminas wrote:
I'd update the boostrap, if I could figure out where in svn is the thing called "ztk_1_1". Buildbot makes it unreasonably hard to figure this stuff out (this is why I publish the master.cfg of my buildbot at http://zope3.pov.lt/buildbot/.
svn://svn.zope.org/repos/main/zope.wineggbuilder/trunk/master.cfg at your service ;-) Just included that info on the root page.
I noticed the link on the root page already, and felt silly that I hadn't noticed it before. I was going to send an email apologizing for my lack of attention. :-)
Speaking of which, it's red as a very red thing, but I haven't seen any failure emails! What's going on there?).
buildbot 0.8.x being subtly incompatible with buildbot 0.7.x config files, of course. The message_formatter from [1] no longer works: now you need to use master_status.getTitle() instead of master_status.getProjectName() [1] http://docs.zope.org/zopetoolkit/process/buildbots.html#informing-the-zope-d... I wanted to fix the zopetoolkit docs, but I forgot which SVN repository contains them. (If they were moved to github and readthedocs, I'd have an "Edit on github" link in the sidebar and could fix it right away. Hint, hint.)
I'm guessing this might be svn+ssh://svn.zope.org/repos/main/zopetoolkit/branches/1.1
It is,
http://winbot.zope.org/builders/ztk_11%20py_254_win32/builds/699/steps/svn-i...
tells you the URL
Awesome! And yeah, sorry for my lack of attention. And general grumpiness -- I haven't had breakfast yet. slouching-back-into-my-cave-ly, Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (3)
-
Adam GROSZER -
Marius Gedminas -
Zope tests summarizer