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
----------------
ZTK 1.0 / Python2.4.6 Linux 64bit
ZTK 1.0 / Python2.5.5 Linux 64bit
ZTK 1.0 / Python2.6.7 Linux 64bit
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
Zope 3.4 KGS / Python2.4.6 64bit linux
Zope 3.4 KGS / Python2.5.5 64bit linux
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
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
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
[1] winbot / ztk_dev py_265_win32
[2] winbot / ztk_dev py_265_win64
[3] winbot / ztk_dev py_270_win32
[4] winbot / ztk_dev py_270_win64
Non-OK results
--------------
[1] FAILED winbot / ztk_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2012-March/059261.html
[2] FAILED winbot / ztk_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2012-March/059262.html
[3] FAILED winbot / ztk_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2012-March/059263.html
[4] FAILED winbot / ztk_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2012-March/059264.html
_______________________________________________
Zope-Dev maillist - Zope...@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 )
Reports received
----------------
Non-OK results
--------------
https://mail.zope.org/pipermail/zope-tests/2012-March/059300.html
[2] FAILED winbot / ztk_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2012-March/059301.html
[3] FAILED winbot / ztk_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2012-March/059302.html
[4] FAILED winbot / ztk_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2012-March/059303.html
On 03/14/2012 09:00 PM, Zope tests summarizer wrote:
> [1] FAILED winbot / ztk_dev py_265_win32
> https://mail.zope.org/pipermail/zope-tests/2012-March/059300.html
>
>
> [2] FAILED winbot / ztk_dev py_265_win64
> https://mail.zope.org/pipermail/zope-tests/2012-March/059301.html
>
>
> [3] FAILED winbot / ztk_dev py_270_win32
> https://mail.zope.org/pipermail/zope-tests/2012-March/059302.html
>
>
> [4] FAILED winbot / ztk_dev py_270_win64
> https://mail.zope.org/pipermail/zope-tests/2012-March/059303.html
All fail with::
While:
Installing test-zopeapp.
Getting distribution for 'ZODB3>=3.10'.
Error: Picked: zodb3 = 3.10.5
Ideas?
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tse...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9h3v4ACgkQ+gerLs4ltQ5a/gCbBXwjIv2T7nFmIaF4K3Z1DQbL
SNoAoKxct+xXiMo5pXKm9+iPVZrfcp42
=2y5L
-----END PGP SIGNATURE-----
I think I fixed that in zope.app.publication now. Note that these are
dev builds, so they use all packages from SVN.
z.a.publication added a new requirement for ZODB3>=3.10. But ZODB on
its 3.10 branch notes its version as 3.10dev. As 3.10dev < 3.10 the
check failed.
Relaxing the check to "ZODB3>=3.10dev" should fix this. Alternatively
"ZODB3>3.10.999" would have worked as well.
Hanno
Eh? That implies that 3.10 will be the next released version from that
branch, which makes no sense, given that the last release was 3.10.5.
The branch should identify itself as 3.10.6dev.
> As 3.10dev < 3.10 the
> check failed.
>
> Relaxing the check to "ZODB3>=3.10dev" should fix this. Alternatively
> "ZODB3>3.10.999" would have worked as well.
Perhaps you meant ZODB3 > 3.9.999?
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
I think Jim always used a slightly different approach, preferring to
keep any version numbers out of SVN, so we are "lucky" it states 3.10
at all. As the ZODB isn't part of the ZTK, the ZTK guidelines on
version numbers don't apply. I don't see any real issues here.
>> As 3.10dev < 3.10 the
>> check failed.
>>
>> Relaxing the check to "ZODB3>=3.10dev" should fix this. Alternatively
>> "ZODB3>3.10.999" would have worked as well.
>
> Perhaps you meant ZODB3 > 3.9.999?
yes, sure.