zope-tests - FAILED: 14, OK: 7
This is the summary for test reports received on the zope-tests list between 2013-07-09 00:00:00 UTC and 2013-07-10 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] Failure - zopetoolkit_trunk - Build # 320 Fixed - zopetoolkit_trunk - Build # 319 Fixed - zopetoolkit_trunk - Build # 324 [2] Still Failing - zopetoolkit_trunk - Build # 318 [3] Still Failing - zopetoolkit_trunk - Build # 321 [4] Still Failing - zopetoolkit_trunk - Build # 322 [5] Still Failing - zopetoolkit_trunk - Build # 323 [6] winbot / ZODB_dev py_265_win32 [7] winbot / ZODB_dev py_265_win64 [8] winbot / ZODB_dev py_270_win32 [9] winbot / ZODB_dev py_270_win64 [10] winbot / z3c.layer.pagelet_py_265_32 [11] winbot / zc.sourcefactory_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 [12] winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [13] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [14] winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED Failure - zopetoolkit_trunk - Build # 320 https://mail.zope.org/pipermail/zope-tests/2013-July/077754.html [2] FAILED Still Failing - zopetoolkit_trunk - Build # 318 https://mail.zope.org/pipermail/zope-tests/2013-July/077752.html [3] FAILED Still Failing - zopetoolkit_trunk - Build # 321 https://mail.zope.org/pipermail/zope-tests/2013-July/077755.html [4] FAILED Still Failing - zopetoolkit_trunk - Build # 322 https://mail.zope.org/pipermail/zope-tests/2013-July/077756.html [5] FAILED Still Failing - zopetoolkit_trunk - Build # 323 https://mail.zope.org/pipermail/zope-tests/2013-July/077757.html [6] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077767.html [7] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077768.html [8] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077769.html [9] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077770.html [10] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077751.html [11] FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077750.html [12] FAILED winbot / ztk_10 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077761.html [13] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077764.html [14] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077766.html
Hi, zopetoolkit-trunk under linux is fine. I create a fresh buildout every time, now I have to create a virtualenv with --distribute, then I have to upgrade setuptools. Until I tested all combinations, I had a bunch of failed test runs. I have a feeling I'll need to buy rubber chickens for the next iterations. On Thu, Jul 11, 2013 at 1:01 AM, Zope tests summarizer <noreply@zope.org>wrote:
This is the summary for test reports received on the zope-tests list between 2013-07-09 00:00:00 UTC and 2013-07-10 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] Failure - zopetoolkit_trunk - Build # 320 Fixed - zopetoolkit_trunk - Build # 319 Fixed - zopetoolkit_trunk - Build # 324 [2] Still Failing - zopetoolkit_trunk - Build # 318 [3] Still Failing - zopetoolkit_trunk - Build # 321 [4] Still Failing - zopetoolkit_trunk - Build # 322 [5] Still Failing - zopetoolkit_trunk - Build # 323 [6] winbot / ZODB_dev py_265_win32 [7] winbot / ZODB_dev py_265_win64 [8] winbot / ZODB_dev py_270_win32 [9] winbot / ZODB_dev py_270_win64 [10] winbot / z3c.layer.pagelet_py_265_32 [11] winbot / zc.sourcefactory_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 [12] winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [13] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [14] winbot / ztk_11 py_270_win64
Non-OK results --------------
[1] FAILED Failure - zopetoolkit_trunk - Build # 320 https://mail.zope.org/pipermail/zope-tests/2013-July/077754.html
[2] FAILED Still Failing - zopetoolkit_trunk - Build # 318 https://mail.zope.org/pipermail/zope-tests/2013-July/077752.html
[3] FAILED Still Failing - zopetoolkit_trunk - Build # 321 https://mail.zope.org/pipermail/zope-tests/2013-July/077755.html
[4] FAILED Still Failing - zopetoolkit_trunk - Build # 322 https://mail.zope.org/pipermail/zope-tests/2013-July/077756.html
[5] FAILED Still Failing - zopetoolkit_trunk - Build # 323 https://mail.zope.org/pipermail/zope-tests/2013-July/077757.html
[6] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077767.html
[7] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077768.html
[8] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077769.html
[9] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077770.html
[10] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077751.html
[11] FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077750.html
[12] FAILED winbot / ztk_10 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077761.html
[13] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077764.html
[14] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077766.html
_______________________________________________ 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 )
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/11/2013 03:55 AM, Patrick Gerken wrote:
now I have to create a virtualenv with --distribute, then I have to upgrade setuptools
We should be upgrading all our projects to zc.buildout 2.2, which drops 'distribute'. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlHexM0ACgkQ+gerLs4ltQ6wyQCgkrbTYpPBYdzsJC4nE1ME+UgB ZvQAnjvNL0CRY5Td7DcWdxhNa0ySIwLo =yMRe -----END PGP SIGNATURE-----
On Jul 11, 2013, at 16:44 , Tres Seaver <tseaver@palladion.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/11/2013 03:55 AM, Patrick Gerken wrote:
now I have to create a virtualenv with --distribute, then I have to upgrade setuptools
We should be upgrading all our projects to zc.buildout 2.2, which drops 'distribute'.
FWIW I tried to upgrade a few projects to zc.buildout 2.2 today but had to revert to a buildout 1.x due to conflicts with an OS-provided pkg-resources sourced from distribute that I could not uninstall. Wichert.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/11/2013 01:05 PM, Wichert Akkerman wrote:
FWIW I tried to upgrade a few projects to zc.buildout 2.2 today but had to revert to a buildout 1.x due to conflicts with an OS-provided pkg-resources sourced from distribute that I could not uninstall.
Patient: "Doctor, when I drink iced tea I get a cold stabbing pain in my eye!" Doctor: "Take out the spoon!" (In other words, if the system python is hosing you, quit using it). If the system python provide command-line flags for suppressing site-paacakges, you might be able to use them to bootstrap. Or build a virtualenv '--without-setuptools' and use that to boostrap. Or just build your own Python and be done. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlHfT/EACgkQ+gerLs4ltQ44JQCePWPiYBa4hG1RP+XlwAAxigVq 0jYAn0PkuUFKTaG6kpWCMh3F4DA0NViD =nDCl -----END PGP SIGNATURE-----
On Jul 12, 2013, at 02:38, Tres Seaver <tseaver@palladion.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/11/2013 01:05 PM, Wichert Akkerman wrote:
FWIW I tried to upgrade a few projects to zc.buildout 2.2 today but had to revert to a buildout 1.x due to conflicts with an OS-provided pkg-resources sourced from distribute that I could not uninstall.
Patient: "Doctor, when I drink iced tea I get a cold stabbing pain in my eye!"
Doctor: "Take out the spoon!"
(In other words, if the system python is hosing you, quit using it).
If the system python provide command-line flags for suppressing site-paacakges, you might be able to use them to bootstrap. Or build a virtualenv '--without-setuptools' and use that to boostrap. Or just build your own Python and be done.
The recommendation to compile your own python comes up often, but from an operational point of view is not a realistic thing to do. I want to use a system Python since I want to get automatic (security) updates from my OS instead of having to deal with them manually. virtualenv might work, but then again using buildout 1.7 which essentially has virtualenv built in still seems like a simpler solution. Wichert.
participants (4)
-
Patrick Gerken -
Tres Seaver -
Wichert Akkerman -
Zope tests summarizer