Re: zope-tests - FAILED: 7, OK: 16

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

_______________________________________________
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)

iD8DBQFRGfYPkVdEXeem148RAgBlAJ97f2rNEjAIIwYihQo9lfx4smSVnwCgiIsh
C2hsYX0NRYE6EgY30RS5BpY=
=L5TP
-----END PGP SIGNATURE-----