Re: [Zope-dev] zope-tests - FAILED: 86, OK: 5
On 06/03/2013 04:59 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/03/2013 09:04 AM, Adam GROSZER wrote: On 06/03/2013 02:37 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/02/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-06-01 00:00:00 UTC and 2013-06-02 00:00:00 UTC: I'm not sure where we are with these failures. I can't reproduce the exact failures on fresh checkouts, but I believe we are in a weird state due to a combination of factors: - - distribute / setuptools merger - - PyPI now HTTPS-only - - PyPI CDN caching? I think we should be aiming to switch our bootstraps over ASAP to pick up setuptools 0.7: it doesn't appear to be simple at the moment to get that installed, as there is no 'ez_setup.py' in the beta location: https://bitbucket.org/pypa/setuptools/downloads I think it's the first. It seems to be a distribute vs setuptools fight. I recently installed distribute in site-packages, but that does not seem to help. Would it help to update to setuptools-0.7 in the 'site-packages' (removing distribute completely)? I have the feeling that the faster we put setuptools-0.6 and distribute behind us, the better off we will be. I've played with it some this morning: the major issue for our buildouts is to get an 'ez_setup.py' selected which doesn't look for setuptools-0.7 on PyPI -- I don't quite know why, but it is only available here: https://bitbucket.org/pypa/setuptools/downloads The attached file woks for me using e.g.: $ /path/to/python bootstrap.py --setup-source=file:///tmp/ez_setup.py Seems like installing setuptools-0.7.1.tar.gz in site-packages solved it. No need to add --setup-source to bootstrap. See here: http://winbot.zope.org/builders/zope.annotation_py_265_32/builds/885 As next if setuptools-0.7 is the ultimate solution we should push the guys to use and respect tests on windows. That might catch problems earlier. -- Best regards, Adam GROSZER -- Quote of the day: A woman is like a teabag -- you can't tell how strong she is until you put her in hot water. - Nancy Reagan ___ 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 )
Re: [Zope-dev] RFC: branch updating zc.buildout and bootstraps to use setuptools 0.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/04/2013 10:13 AM, Leonardo Rochael Almeida wrote: On Mon, Jun 3, 2013 at 10:25 PM, Tres Seaver tsea...@palladion.com wrote: [...] I would like some help getting the manuel + renormalizer + doctest tests working, or at least getting the spurious output differences smoothed away so we can see real semantic changes, if any. Which tests do you need help with? zc.buildout ones on your branch or Zope repo projects running with your branch? I need help with the buildout tests themselves: the combination of manuel + regext nromalizers + doctests makes my head hurt. If the former, wouldn't it be better to (also) contact the buildout development list [1]? Ugh, Google Groups I guess that is the right place to ask, though; I had forgotten that there was a separate list. If the latter which steps do we need to follow to get to the failures you need help with? [1] https://groups.google.com/forum/?fromgroups#!forum/buildout-development I haven't gotten far enough with it to try building the ZTK projects, etc. It needs to pass its own tests first. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEUEARECAAYFAlGuAYYACgkQ+gerLs4ltQ4rIQCXR0lHLq9vSgbFLgljbl+ws1uL 9QCgtdLevOwQtbVTYm8Z8/fIFuWgkIk= =PRCv -END PGP SIGNATURE- ___ 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 )
[Zope-dev] zope-tests - FAILED: 75, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-06-03 00:00:00 UTC and 2013-06-04 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 # 286 [1]winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 [2]winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [3]winbot / ZODB_dev py_270_win64 [4]winbot / z3c.authenticator_py_265_32 [5]winbot / z3c.breadcrumb_py_265_32 [6]winbot / z3c.configurator_py_265_32 [7]winbot / z3c.contents_py_265_32 [8]winbot / z3c.coverage_py_265_32 [9]winbot / z3c.form_py_265_32 [10] winbot / z3c.formui_py_265_32 [11] winbot / z3c.json_py_265_32 [12] winbot / z3c.jsontree_py_265_32 [13] winbot / z3c.language.switch_py_265_32 [14] winbot / z3c.layer.pagelet_py_265_32 [15] winbot / z3c.layer.ready2go_py_265_32 [16] winbot / z3c.macro_py_265_32 [17] winbot / z3c.menu.ready2go_py_265_32 [18] winbot / z3c.pagelet_py_265_32 [19] winbot / z3c.password_py_265_32 [20] winbot / z3c.ptcompat_py_265_32 [21] winbot / z3c.sampledata_py_265_32 [22] winbot / z3c.table_py_265_32 [23] winbot / z3c.tabular_py_265_32 [24] winbot / z3c.template_py_265_32 [25] winbot / z3c.testing_py_265_32 [26] winbot / zc.lockfile_py_265_32 [27] winbot / zc.queue_py_265_32 [28] winbot / zc.sourcefactory_py_265_32 [29] winbot / zope.annotation_py_265_32 [30] winbot / zope.app.authentication_py_265_32 [31] winbot / zope.app.dependable_py_265_32 [32] winbot / zope.app.http_py_265_32 [33] winbot / zope.app.publication_py_265_32 [34] winbot / zope.app.publisher_py_265_32 [35] winbot / zope.applicationcontrol_py_265_32 [36] winbot / zope.authentication_py_265_32 [37] winbot / zope.browsermenu_py_265_32 [38] winbot / zope.browserpage_py_265_32 [39] winbot / zope.browserresource_py_265_32 [40] winbot / zope.component_py_265_32 [41] winbot / zope.container_py_265_32 [42] winbot / zope.contentprovider_py_265_32 [43] winbot / zope.datetime_py_265_32 [44] winbot / zope.deferredimport_py_265_32 [45] winbot / zope.dublincore_py_265_32 [46] winbot / zope.error_py_265_32 [47] winbot / zope.exceptions_py_265_32 [48] winbot / zope.formlib_py_265_32 [49] winbot / zope.generations_py_265_32 [50] winbot / zope.i18n_py_265_32 [51] winbot / zope.intid_py_265_32 [52] winbot / zope.location_py_265_32 [53] winbot / zope.login_py_265_32 [54] winbot / zope.mimetype_py_265_32 [55] winbot / zope.minmax_py_265_32 [56] winbot / zope.pagetemplate_py_265_32 [57] winbot / zope.pluggableauth_py_265_32 [58] winbot / zope.principalannotation_py_265_32 [59] winbot / zope.principalregistry_py_265_32 [60] winbot / zope.processlifetime_py_265_32 [61] winbot / zope.ptresource_py_265_32 [62] winbot / zope.ramcache_py_265_32 [63] winbot / zope.renderer_py_265_32 [64] winbot / zope.securitypolicy_py_265_32 [65] winbot / zope.sendmail_py_265_32 [66] winbot / zope.sequencesort_py_265_32 [67] winbot / zope.session_py_265_32 [68] winbot / zope.structuredtext_py_265_32 [69] winbot / zope.tales_py_265_32 [70] winbot / zope.testrunner_py_265_32 [71] winbot / zope.traversing_py_265_32 [72] winbot / zope.viewlet_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 [73] winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [74] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [75] winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED winbot / ZEO_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075846.html [2]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/075789.html [3]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/075791.html [4]FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075795.html [5]FAILED winbot / z3c.breadcrumb_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075817.html [6]FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075800.html [7]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075848.html [8]FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075799.html [9]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075832.html [10] FAILED winbot / z3c.formui_py_265_32
Re: [Zope-dev] zope-tests - FAILED: 86, OK: 5
On 06/04/2013 10:08 AM, Adam GROSZER wrote: On 06/03/2013 04:59 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/03/2013 09:04 AM, Adam GROSZER wrote: On 06/03/2013 02:37 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/02/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-06-01 00:00:00 UTC and 2013-06-02 00:00:00 UTC: I'm not sure where we are with these failures. I can't reproduce the exact failures on fresh checkouts, but I believe we are in a weird state due to a combination of factors: - - distribute / setuptools merger - - PyPI now HTTPS-only - - PyPI CDN caching? I think we should be aiming to switch our bootstraps over ASAP to pick up setuptools 0.7: it doesn't appear to be simple at the moment to get that installed, as there is no 'ez_setup.py' in the beta location: https://bitbucket.org/pypa/setuptools/downloads I think it's the first. It seems to be a distribute vs setuptools fight. I recently installed distribute in site-packages, but that does not seem to help. Would it help to update to setuptools-0.7 in the 'site-packages' (removing distribute completely)? I have the feeling that the faster we put setuptools-0.6 and distribute behind us, the better off we will be. I've played with it some this morning: the major issue for our buildouts is to get an 'ez_setup.py' selected which doesn't look for setuptools-0.7 on PyPI -- I don't quite know why, but it is only available here: https://bitbucket.org/pypa/setuptools/downloads The attached file woks for me using e.g.: $ /path/to/python bootstrap.py --setup-source=file:///tmp/ez_setup.py Seems like installing setuptools-0.7.1.tar.gz in site-packages solved it. No need to add --setup-source to bootstrap. See here: http://winbot.zope.org/builders/zope.annotation_py_265_32/builds/885 As next if setuptools-0.7 is the ultimate solution we should push the guys to use and respect tests on windows. That might catch problems earlier. Meeeh now the other half seems to fail... We should decide what's the current stable mix of tools, then a script or someone needs to go through all packages. Or, I'll use again a central bootstrap.py for all packages. Which is kind of misleading in tests. -- Best regards, Adam GROSZER -- Quote of the day: The probability that we may fail in the struggle ought not to deter us from the support of a cause we believe to be just. - Abraham Lincoln ___ 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 )
