zope-tests - FAILED: 86, OK: 5
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: 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 # 284 [1] winbot / BTrees_py_265_32 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 [5] winbot / persistent_py_265_32 [6] winbot / transaction_py_265_32 [7] winbot / z3c.baseregistry_py_265_32 [8] winbot / z3c.batching_py_265_32 [9] winbot / z3c.batching_py_265_32 [10] winbot / z3c.jsonrpc_py_265_32 [11] winbot / z3c.jsonrpcproxy_py_265_32 [12] winbot / z3c.language.negotiator_py_265_32 [13] winbot / z3c.language.session_py_265_32 [14] winbot / z3c.pdftemplate_py_265_32 [15] winbot / z3c.recipe.paster_py_265_32 [16] winbot / z3c.viewtemplate_py_265_32 [17] winbot / z3c.xmlhttp_py_265_32 [18] winbot / z3c.zrtresource_py_265_32 [19] winbot / zc.catalog_py_265_32 [20] winbot / zc.configuration_py_265_32 [21] winbot / zc.i18n_py_265_32 [22] winbot / zc.monitor_py_265_32 [23] winbot / zc.ngi_py_265_32 [24] winbot / zc.ngi_py_265_32 [25] winbot / zc.resourcelibrary_py_265_32 [26] winbot / zc.table_py_265_32 [27] winbot / zc.table_py_265_32 [28] winbot / zope.annotation_py_265_32 [29] winbot / zope.app.applicationcontrol_py_265_32 [30] winbot / zope.app.appsetup_py_265_32 [31] winbot / zope.app.appsetup_py_265_32 [32] winbot / zope.app.basicskin_py_265_32 [33] winbot / zope.app.basicskin_py_265_32 [34] winbot / zope.app.broken_py_265_32 [35] winbot / zope.app.broken_py_265_32 [36] winbot / zope.app.component_py_265_32 [37] winbot / zope.app.container_py_265_32 [38] winbot / zope.app.content_py_265_32 [39] winbot / zope.app.debug_py_265_32 [40] winbot / zope.app.error_py_265_32 [41] winbot / zope.app.exception_py_265_32 [42] winbot / zope.app.folder_py_265_32 [43] winbot / zope.app.form_py_265_32 [44] winbot / zope.app.generations_py_265_32 [45] winbot / zope.app.i18n_py_265_32 [46] winbot / zope.app.interface_py_265_32 [47] winbot / zope.app.interface_py_265_32 [48] winbot / zope.app.localpermission_py_265_32 [49] winbot / zope.app.localpermission_py_265_32 [50] winbot / zope.app.pagetemplate_py_265_32 [51] winbot / zope.app.principalannotation_py_265_32 [52] winbot / zope.app.principalannotation_py_265_32 [53] winbot / zope.app.publisher_py_265_32 [54] winbot / zope.app.publisher_py_265_32 [55] winbot / zope.app.rotterdam_py_265_32 [56] winbot / zope.app.schema_py_265_32 [57] winbot / zope.app.server_py_265_32 [58] winbot / zope.app.session_py_265_32 [59] winbot / zope.app.testing_py_265_32 [60] winbot / zope.app.wsgi_py_265_32 [61] winbot / zope.app.zcmlfiles_py_265_32 [62] winbot / zope.app.zcmlfiles_py_265_32 [63] winbot / zope.app.zopeappgenerations_py_265_32 [64] winbot / zope.browser_py_265_32 [65] winbot / zope.configuration_py_265_32 [66] winbot / zope.contenttype_py_265_32 [67] winbot / zope.copy_py_265_32 [68] winbot / zope.deprecation_py_265_32 [69] winbot / zope.dottedname_py_265_32 [70] winbot / zope.event_py_265_32 [71] winbot / zope.filerepresentation_py_265_32 [72] winbot / zope.hookable_py_265_32 [73] winbot / zope.i18nmessageid_py_265_32 [74] winbot / zope.interface_py_265_32 [75] winbot / zope.lifecycleevent_py_265_32 [76] winbot / zope.proxy_py_265_32 [77] winbot / zope.schema_py_265_32 [78] winbot / zope.server_py_265_32 [79] winbot / zope.size_py_265_32 [80] winbot / zope.testbrowser_py_265_32 [81] winbot / zope.testing_py_265_32 winbot / ztk_10 py_254_win32 [82] winbot / ztk_10 py_265_win32 [83] winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 [84] winbot / ztk_11 py_265_win32 [85] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [86] winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / BTrees_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075681.html [2] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-June/075623.html [3] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/075624.html [4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/075626.html [5] FAILED winbot / persistent_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075641.html [6] FAILED winbot / transaction_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075656.html [7] FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075680.html [8] FAILED winbot / z3c.batching_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075652.html [9] FAILED winbot / z3c.batching_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075610.html [10] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075665.html [11] FAILED winbot / z3c.jsonrpcproxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075655.html [12] FAILED winbot / z3c.language.negotiator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075627.html [13] FAILED winbot / z3c.language.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075642.html [14] FAILED winbot / z3c.pdftemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075636.html [15] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075638.html [16] FAILED winbot / z3c.viewtemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075670.html [17] FAILED winbot / z3c.xmlhttp_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075663.html [18] FAILED winbot / z3c.zrtresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075639.html [19] FAILED winbot / zc.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075688.html [20] FAILED winbot / zc.configuration_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075676.html [21] FAILED winbot / zc.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075689.html [22] FAILED winbot / zc.monitor_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075646.html [23] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075651.html [24] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075603.html [25] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075640.html [26] FAILED winbot / zc.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075673.html [27] FAILED winbot / zc.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075607.html [28] FAILED winbot / zope.annotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075682.html [29] FAILED winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075672.html [30] FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075654.html [31] FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075604.html [32] FAILED winbot / zope.app.basicskin_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075657.html [33] FAILED winbot / zope.app.basicskin_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075609.html [34] FAILED winbot / zope.app.broken_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075653.html [35] FAILED winbot / zope.app.broken_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075611.html [36] FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075666.html [37] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075690.html [38] FAILED winbot / zope.app.content_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075661.html [39] FAILED winbot / zope.app.debug_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075631.html [40] FAILED winbot / zope.app.error_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075628.html [41] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075647.html [42] FAILED winbot / zope.app.folder_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075679.html [43] FAILED winbot / zope.app.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075630.html [44] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075669.html [45] FAILED winbot / zope.app.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075674.html [46] FAILED winbot / zope.app.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075692.html [47] FAILED winbot / zope.app.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075612.html [48] FAILED winbot / zope.app.localpermission_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075677.html [49] FAILED winbot / zope.app.localpermission_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075608.html [50] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075629.html [51] FAILED winbot / zope.app.principalannotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075687.html [52] FAILED winbot / zope.app.principalannotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075605.html [53] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075650.html [54] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075613.html [55] FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075644.html [56] FAILED winbot / zope.app.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075693.html [57] FAILED winbot / zope.app.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075633.html [58] FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075632.html [59] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075635.html [60] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075662.html [61] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075645.html [62] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075606.html [63] FAILED winbot / zope.app.zopeappgenerations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075671.html [64] FAILED winbot / zope.browser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075685.html [65] FAILED winbot / zope.configuration_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075634.html [66] FAILED winbot / zope.contenttype_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075668.html [67] FAILED winbot / zope.copy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075686.html [68] FAILED winbot / zope.deprecation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075643.html [69] FAILED winbot / zope.dottedname_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075691.html [70] FAILED winbot / zope.event_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075637.html [71] FAILED winbot / zope.filerepresentation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075683.html [72] FAILED winbot / zope.hookable_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075684.html [73] FAILED winbot / zope.i18nmessageid_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075664.html [74] FAILED winbot / zope.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075667.html [75] FAILED winbot / zope.lifecycleevent_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075648.html [76] FAILED winbot / zope.proxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075678.html [77] FAILED winbot / zope.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075660.html [78] FAILED winbot / zope.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075649.html [79] FAILED winbot / zope.size_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075659.html [80] FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075675.html [81] FAILED winbot / zope.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075658.html [82] FAILED winbot / ztk_10 py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-June/075616.html [83] FAILED winbot / ztk_10 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/075617.html [84] FAILED winbot / ztk_11 py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-June/075619.html [85] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/075620.html [86] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/075622.html
-----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 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/ iEYEARECAAYFAlGsjhoACgkQ+gerLs4ltQ4+SACglPxJ5J5b7eJV5yUfADFVjeAR bJsAoNJYhnaciMoGMqkP14KRGsFiO7ux =qGub -----END PGP SIGNATURE-----
On Jun 3, 2013, at 14:37 , Tres Seaver <tseaver@palladion.com> 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:
It also doesn't help that buildout 2 switched to requiring distribute just before distributed was merged into setuptools again. Wichert.
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:
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. -- Best regards, Adam GROSZER -- Quote of the day: A man without God is not like a cake without raisins; he is like a cake without the flour and milk; he lacks the essential ingredients... - Bishop Fulton J. Sheen
-----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:
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 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/ iEYEARECAAYFAlGsr2oACgkQ+gerLs4ltQ4fcwCcCKice5D4MObbCuUEkeq88AT3 F+UAoI5Jlfwa44MsmfpPOO4Z1i9kVfO0 =Iiof -----END PGP SIGNATURE-----
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:
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
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:
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
participants (5)
-
Adam GROSZER -
Adam GROSZER -
Tres Seaver -
Wichert Akkerman -
Zope tests summarizer