zope-tests - FAILED: 119, OK: 8
This is the summary for test reports received on the zope-tests list between 2014-12-15 00:00:00 UTC and 2014-12-16 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] Still Failing - zopetoolkit_trunk - Build # 855 [2] winbot / BTrees_py_265_32 [3] winbot / ZODB_dev py_265_win32 [4] winbot / ZODB_dev py_265_win64 [5] winbot / ZODB_dev py_270_win32 [6] winbot / ZODB_dev py_270_win64 [7] winbot / persistent_py_265_32 [8] winbot / z3c.baseregistry_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.layer.pagelet_py_265_32 [15] winbot / z3c.layer.ready2go_py_265_32 [16] winbot / z3c.layer.ready2go_py_265_32 [17] winbot / z3c.recipe.paster_py_265_32 [18] winbot / z3c.viewtemplate_py_265_32 [19] winbot / z3c.viewtemplate_py_265_32 [20] winbot / z3c.xmlhttp_py_265_32 [21] winbot / z3c.zrtresource_py_265_32 [22] winbot / zc.catalog_py_265_32 [23] winbot / zc.configuration_py_265_32 [24] winbot / zc.i18n_py_265_32 [25] winbot / zc.monitor_py_265_32 [26] winbot / zc.ngi_py_265_32 [27] winbot / zc.ngi_py_265_32 [28] winbot / zc.resourcelibrary_py_265_32 [29] winbot / zc.table_py_265_32 [30] winbot / zodbpickle_py_265_32 [31] winbot / zope.annotation_py_265_32 [32] winbot / zope.annotation_py_265_32 [33] winbot / zope.app.applicationcontrol_py_265_32 [34] winbot / zope.app.appsetup_py_265_32 [35] winbot / zope.app.basicskin_py_265_32 [36] winbot / zope.app.broken_py_265_32 [37] winbot / zope.app.component_py_265_32 [38] winbot / zope.app.container_py_265_32 [39] winbot / zope.app.content_py_265_32 [40] winbot / zope.app.debug_py_265_32 [41] winbot / zope.app.dependable_py_265_32 [42] winbot / zope.app.error_py_265_32 [43] winbot / zope.app.exception_py_265_32 [44] winbot / zope.app.exception_py_265_32 [45] winbot / zope.app.folder_py_265_32 [46] winbot / zope.app.form_py_265_32 [47] winbot / zope.app.form_py_265_32 [48] winbot / zope.app.generations_py_265_32 [49] winbot / zope.app.i18n_py_265_32 [50] winbot / zope.app.interface_py_265_32 [51] winbot / zope.app.localpermission_py_265_32 [52] winbot / zope.app.pagetemplate_py_265_32 [53] winbot / zope.app.principalannotation_py_265_32 [54] winbot / zope.app.publication_py_265_32 [55] winbot / zope.app.publisher_py_265_32 [56] winbot / zope.app.rotterdam_py_265_32 [57] winbot / zope.app.schema_py_265_32 [58] winbot / zope.app.security_py_265_32 [59] winbot / zope.app.security_py_265_32 [60] winbot / zope.app.server_py_265_32 [61] winbot / zope.app.session_py_265_32 [62] winbot / zope.app.session_py_265_32 [63] winbot / zope.app.testing_py_265_32 [64] winbot / zope.app.wsgi_py_265_32 [65] winbot / zope.app.zcmlfiles_py_265_32 [66] winbot / zope.app.zopeappgenerations_py_265_32 [67] winbot / zope.applicationcontrol_py_265_32 [68] winbot / zope.applicationcontrol_py_265_32 [69] winbot / zope.authentication_py_265_32 [70] winbot / zope.browser_py_265_32 [71] winbot / zope.browsermenu_py_265_32 [72] winbot / zope.browserpage_py_265_32 [73] winbot / zope.browserresource_py_265_32 [74] winbot / zope.browserresource_py_265_32 [75] winbot / zope.cachedescriptors_py_265_32 [76] winbot / zope.catalog_py_265_32 [77] winbot / zope.catalog_py_265_32 [78] winbot / zope.componentvocabulary_py_265_32 [79] winbot / zope.contentprovider_py_265_32 [80] winbot / zope.contentprovider_py_265_32 [81] winbot / zope.contenttype_py_265_32 [82] winbot / zope.copypastemove_py_265_32 [83] winbot / zope.datetime_py_265_32 [84] winbot / zope.datetime_py_265_32 [85] winbot / zope.deferredimport_py_265_32 [86] winbot / zope.dottedname_py_265_32 [87] winbot / zope.dublincore_py_265_32 [88] winbot / zope.error_py_265_32 [89] winbot / zope.filerepresentation_py_265_32 [90] winbot / zope.formlib_py_265_32 [91] winbot / zope.generations_py_265_32 [92] winbot / zope.generations_py_265_32 [93] winbot / zope.index_py_265_32 [94] winbot / zope.intid_py_265_32 [95] winbot / zope.keyreference_py_265_32 [96] winbot / zope.lifecycleevent_py_265_32 [97] winbot / zope.login_py_265_32 [98] winbot / zope.mimetype_py_265_32 [99] winbot / zope.minmax_py_265_32 [100] winbot / zope.pagetemplate_py_265_32 [101] winbot / zope.password_py_265_32 [102] winbot / zope.principalannotation_py_265_32 [103] winbot / zope.principalregistry_py_265_32 [104] winbot / zope.ptresource_py_265_32 [105] winbot / zope.ptresource_py_265_32 [106] winbot / zope.publisher_py_265_32 [107] winbot / zope.publisher_py_265_32 [108] winbot / zope.ramcache_py_265_32 [109] winbot / zope.renderer_py_265_32 [110] winbot / zope.securitypolicy_py_265_32 [111] winbot / zope.sendmail_py_265_32 [112] winbot / zope.server_py_265_32 [113] winbot / zope.session_py_265_32 [114] winbot / zope.session_py_265_32 [115] winbot / zope.size_py_265_32 [116] winbot / zope.structuredtext_py_265_32 [117] winbot / zope.tal_py_265_32 [118] winbot / zope.tales_py_265_32 [119] winbot / zope.traversing_py_265_32 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 Non-OK results -------------- [1] FAILED Still Failing - zopetoolkit_trunk - Build # 855 https://mail.zope.org/pipermail/zope-tests/2014-December/085576.html [2] FAILED winbot / BTrees_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085589.html [3] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2014-December/085585.html [4] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2014-December/085586.html [5] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2014-December/085587.html [6] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2014-December/085588.html [7] FAILED winbot / persistent_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085563.html [8] FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085609.html [9] FAILED winbot / z3c.batching_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085649.html [10] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085604.html [11] FAILED winbot / z3c.jsonrpcproxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085619.html [12] FAILED winbot / z3c.language.negotiator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085595.html [13] FAILED winbot / z3c.language.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085596.html [14] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085607.html [15] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085670.html [16] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085560.html [17] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085601.html [18] FAILED winbot / z3c.viewtemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085671.html [19] FAILED winbot / z3c.viewtemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085561.html [20] FAILED winbot / z3c.xmlhttp_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085627.html [21] FAILED winbot / z3c.zrtresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085613.html [22] FAILED winbot / zc.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085592.html [23] FAILED winbot / zc.configuration_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085617.html [24] FAILED winbot / zc.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085594.html [25] FAILED winbot / zc.monitor_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085635.html [26] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085669.html [27] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085559.html [28] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085622.html [29] FAILED winbot / zc.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085644.html [30] FAILED winbot / zodbpickle_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085633.html [31] FAILED winbot / zope.annotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085665.html [32] FAILED winbot / zope.annotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085555.html [33] FAILED winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085593.html [34] FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085650.html [35] FAILED winbot / zope.app.basicskin_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085646.html [36] FAILED winbot / zope.app.broken_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085639.html [37] FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085628.html [38] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085590.html [39] FAILED winbot / zope.app.content_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085638.html [40] FAILED winbot / zope.app.debug_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085571.html [41] FAILED winbot / zope.app.dependable_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085612.html [42] FAILED winbot / zope.app.error_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085573.html [43] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085659.html [44] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085549.html [45] FAILED winbot / zope.app.folder_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085565.html [46] FAILED winbot / zope.app.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085656.html [47] FAILED winbot / zope.app.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085546.html [48] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085624.html [49] FAILED winbot / zope.app.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085610.html [50] FAILED winbot / zope.app.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085643.html [51] FAILED winbot / zope.app.localpermission_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085645.html [52] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085591.html [53] FAILED winbot / zope.app.principalannotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085567.html [54] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085608.html [55] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085652.html [56] FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085616.html [57] FAILED winbot / zope.app.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085574.html [58] FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085664.html [59] FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085554.html [60] FAILED winbot / zope.app.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085631.html [61] FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085667.html [62] FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085557.html [63] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085568.html [64] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085630.html [65] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085653.html [66] FAILED winbot / zope.app.zopeappgenerations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085618.html [67] FAILED winbot / zope.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085662.html [68] FAILED winbot / zope.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085552.html [69] FAILED winbot / zope.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085623.html [70] FAILED winbot / zope.browser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085598.html [71] FAILED winbot / zope.browsermenu_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085629.html [72] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085602.html [73] FAILED winbot / zope.browserresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085663.html [74] FAILED winbot / zope.browserresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085553.html [75] FAILED winbot / zope.cachedescriptors_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085575.html [76] FAILED winbot / zope.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085668.html [77] FAILED winbot / zope.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085558.html [78] FAILED winbot / zope.componentvocabulary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085647.html [79] FAILED winbot / zope.contentprovider_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085660.html [80] FAILED winbot / zope.contentprovider_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085550.html [81] FAILED winbot / zope.contenttype_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085625.html [82] FAILED winbot / zope.copypastemove_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085642.html [83] FAILED winbot / zope.datetime_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085658.html [84] FAILED winbot / zope.datetime_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085548.html [85] FAILED winbot / zope.deferredimport_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085636.html [86] FAILED winbot / zope.dottedname_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085564.html [87] FAILED winbot / zope.dublincore_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085621.html [88] FAILED winbot / zope.error_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085570.html [89] FAILED winbot / zope.filerepresentation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085603.html [90] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085597.html [91] FAILED winbot / zope.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085666.html [92] FAILED winbot / zope.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085556.html [93] FAILED winbot / zope.index_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085640.html [94] FAILED winbot / zope.intid_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085606.html [95] FAILED winbot / zope.keyreference_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085654.html [96] FAILED winbot / zope.lifecycleevent_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085562.html [97] FAILED winbot / zope.login_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085600.html [98] FAILED winbot / zope.mimetype_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085614.html [99] FAILED winbot / zope.minmax_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085615.html [100] FAILED winbot / zope.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085569.html [101] FAILED winbot / zope.password_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085648.html [102] FAILED winbot / zope.principalannotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085632.html [103] FAILED winbot / zope.principalregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085572.html [104] FAILED winbot / zope.ptresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085657.html [105] FAILED winbot / zope.ptresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085547.html [106] FAILED winbot / zope.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085655.html [107] FAILED winbot / zope.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085545.html [108] FAILED winbot / zope.ramcache_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085566.html [109] FAILED winbot / zope.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085605.html [110] FAILED winbot / zope.securitypolicy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085641.html [111] FAILED winbot / zope.sendmail_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085620.html [112] FAILED winbot / zope.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085599.html [113] FAILED winbot / zope.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085661.html [114] FAILED winbot / zope.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085551.html [115] FAILED winbot / zope.size_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085637.html [116] FAILED winbot / zope.structuredtext_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085626.html [117] FAILED winbot / zope.tal_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085651.html [118] FAILED winbot / zope.tales_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085634.html [119] FAILED winbot / zope.traversing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085611.html
On Wed, Dec 17, 2014 at 01:00:03AM +0100, Zope tests summarizer wrote:
[1] Still Failing - zopetoolkit_trunk - Build # 855
Last build of zopetoolkit_trunk was successful, woohoo! It's pinning buildout to 2.2.4 and setuptools to 7.0, so maybe the woohoo was a bit premature.
[2] winbot / BTrees_py_265_32 ... [119] FAILED winbot / zope.traversing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085611.html
The variety of errors has decreased somewhat. Most of the builds fail with Error: Couldn't find a distribution for 'zc.recipe.egg<2dev,==1.3.0,>1.3.0'. Several fail with Error: There is a version conflict. We already have: zc.recipe.egg 1.3.2 which seems like it could be the same thing? but maybe different buildout version or something? Then we have a couple of The constraint, 4.0.0a3, is not consistent with the requirement, 'zope.security>4.0.0a2'. and one Error: There is a version conflict. We already have: zc.buildout 1.7.1 and one Error: Couldn't find a distribution for 'zope.app.wsgi<3.11,<4.0dev,>=3.12'. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
Marius Gedminas schreef op 17-12-14 10:14:
On Wed, Dec 17, 2014 at 01:00:03AM +0100, Zope tests summarizer wrote:
[1] Still Failing - zopetoolkit_trunk - Build # 855
Last build of zopetoolkit_trunk was successful, woohoo!
It's pinning buildout to 2.2.4 and setuptools to 7.0, so maybe the woohoo was a bit premature.
[2] winbot / BTrees_py_265_32 ... [119] FAILED winbot / zope.traversing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085611.html
The variety of errors has decreased somewhat. Most of the builds fail with
Error: Couldn't find a distribution for 'zc.recipe.egg<2dev,==1.3.0,>1.3.0'.
setuptools version 8 is used, which complains about this stuff. Initial solution would be to make sure setuptools 7.0 or earlier is used. Running bootstrap.py in this buildout (zope.traversing) will give you a bin/buildout with zc.buildout 1.7.1 and the latest setuptools version, which currently is 8.0.4. I suppose this is true for most or all ztk packages. Some solutions are thinkable: - Pin setuptools to 7.0 or earlier. This gives bin/buildout a chance to downgrade from the 8.0.4 that bootstrap is currently giving. I have done that on zope.traversing now. Let's see. - Call 'python bootstrap.py --download-base=http://pypi.zestsoftware.nl/public/oldsetuptools/' or some other web page that has links to at most setuptools 7.0 and possibly zc.buildout. According to the help text of bootstrap.py this should help, but I tried it and it did not work. Maybe it needs to be behind https. - Call 'python2.7 bootstrap.py --setup-source=https://bitbucket.org/pypa/setuptools/raw/7.0/ez_setup.py' so bootstrap calls an ez_setup.py that defaults to setuptools 7.0. Maybe this works on the buildbots, but locally it failed for me: The required version of setuptools (>=7.0) is not available, and can't be installed while this script is running. Please install a more recent version first, using 'easy_install -U setuptools'. (Currently using setuptools 0.9.8 (/Users/mauritsvanrees/buildout/python2.7/python-2.7/lib/python2.7/site-packages)) - Use https://bootstrap.pypa.io/bootstrap-buildout.py and call it with '--version=1.7.1 --setuptools-version=7.0' (or whatever version you prefer). This may be the best solution.
Several fail with
Error: There is a version conflict. We already have: zc.recipe.egg 1.3.2
which seems like it could be the same thing? but maybe different buildout version or something?
Then we have a couple of
The constraint, 4.0.0a3, is not consistent with the requirement, 'zope.security>4.0.0a2'.
and one
Error: There is a version conflict. We already have: zc.buildout 1.7.1
and one
Error: Couldn't find a distribution for 'zope.app.wsgi<3.11,<4.0dev,>=3.12'.
Presumably the errors will disappear when using setuptools 7.0 or earlier. Maybe some will disappear with future 8.x versions. This last one definitely needs an actual fix at some point though. Some package has '<3.11,>=3.12' as version restriction, which is apparently meant to blacklist the 3.11 version. This should become '!=3.11'. See http://legacy.python.org/dev/peps/pep-0440/#version-specifiers -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl
Maurits van Rees schreef op 17-12-14 21:15:
- Use https://bootstrap.pypa.io/bootstrap-buildout.py and call it with '--version=1.7.1 --setuptools-version=7.0' (or whatever version you prefer). This may be the best solution.
For some reason this still ends in a bin/buildout with setuptools 8.0.4. Using '--version=2.2.5 --setuptools-version=7.0' does lead to bin/buildout with those exact versions. Note that running bin/buildout after this may still install other versions, depending on what versions are pinned in the buildout config. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl
On Wed, Dec 17, 2014 at 09:15:45PM +0100, Maurits van Rees wrote:
Marius Gedminas schreef op 17-12-14 10:14:
The variety of errors has decreased somewhat. Most of the builds fail with
Error: Couldn't find a distribution for 'zc.recipe.egg<2dev,==1.3.0,>1.3.0'.
setuptools version 8 is used, which complains about this stuff. Initial solution would be to make sure setuptools 7.0 or earlier is used.
That's a valid short-term solution, but eventually we want to have working builds with setuptools 8 as well.
Running bootstrap.py in this buildout (zope.traversing) will give you a bin/buildout with zc.buildout 1.7.1 and the latest setuptools version, which currently is 8.0.4. I suppose this is true for most or all ztk packages.
Some solutions are thinkable:
- Pin setuptools to 7.0 or earlier. This gives bin/buildout a chance to downgrade from the 8.0.4 that bootstrap is currently giving. I have done that on zope.traversing now. Let's see.
The build succeeds: http://winbot.zope.org/builders/zope.traversing_py_265_32/builds/1436
and one
Error: Couldn't find a distribution for 'zope.app.wsgi<3.11,<4.0dev,>=3.12'.
Presumably the errors will disappear when using setuptools 7.0 or earlier. Maybe some will disappear with future 8.x versions. This last one definitely needs an actual fix at some point though. Some package has
"Some package" is zope.app.publication: https://github.com/zopefoundation/zope.app.publication/blob/011f6dddd42e6c70...
'<3.11,>=3.12' as version restriction, which is apparently meant to blacklist the 3.11 version. This should become '!=3.11'. See http://legacy.python.org/dev/peps/pep-0440/#version-specifiers
I worry that '!=3.11' means a different thing for setuptools < 8.0. Oh well, the only zope.app.wsgi 3.11.x release on PyPI is 3.11.0. I think '!= 3.11.0' would work with all versions of setuptools. And if not, we can bite the bullet and require zope.app.wsgi >= 3.12 for people who want a recent zope.app.publication. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Wed, Dec 17, 2014 at 11:14:26AM +0200, Marius Gedminas wrote:
On Wed, Dec 17, 2014 at 01:00:03AM +0100, Zope tests summarizer wrote:
[1] Still Failing - zopetoolkit_trunk - Build # 855
Last build of zopetoolkit_trunk was successful, woohoo!
It's pinning buildout to 2.2.4 and setuptools to 7.0, so maybe the woohoo was a bit premature.
[2] winbot / BTrees_py_265_32 ... [119] FAILED winbot / zope.traversing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-December/085611.html
The variety of errors has decreased somewhat. Most of the builds fail with
Error: Couldn't find a distribution for 'zc.recipe.egg<2dev,==1.3.0,>1.3.0'.
One of the failing builds was zope.error. I didn't investigate the failure, just noticed that it had a really old bootstrap.py from zc.buildout 1.x days while not actually relying on any buildout 1.x features. I replaced it with a recent bootstrap from https://bootstrap.pypa.io/bootstrap-buildout.py and the build succeeded (on my laptop). Time to mass-migrate zope.* to zc.buildout 2? Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/18/2014 02:35 AM, Marius Gedminas wrote:
Time to mass-migrate zope.* to zc.buildout 2?
Yup. 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) iEYEARECAAYFAlSTOPgACgkQ+gerLs4ltQ4GdQCfWxR7FVk1763ZD8eJayZnH2SB oLcAnjWSsLMPRmj2rta+dCWs8oRhnZhD =oXZv -----END PGP SIGNATURE-----
Marius Gedminas schreef op 17-12-14 10:14:
The variety of errors has decreased somewhat. Most of the builds fail with
Error: Couldn't find a distribution for 'zc.recipe.egg<2dev,==1.3.0,>1.3.0'.
I wondered about this one. Grepping in my eggs directory in */EGG-INFO/requires.txt for zc.recipe.egg I only find z3c.recipe.scripts 1.0.1 that has 'zc.recipe.egg >=1.3.0'. I wonder if somehow this wrongly gets split into the contradicting '==1.3.0,>1.3.0'. Trying it locally for such a failing build (zope.traversing before I pinned setuptools), I see that zc.buildout 1.7.1 is used, which has this in buildout.py: self.versions = { 'zc.recipe.egg': '<2dev', 'zc.recipe.testrunner': '<2dev', } So that is where the '<2dev' comes from. zc/buildout/easy_install.py then has an install method, which combines the version restriction with the requirement in this call: _constrained_requirement_constraint( '<2dev', Requirement.parse('zc.recipe.egg>=1.3.0')) The result of that call is: '<2dev,>1.3.0,==1.3.0' This is silly but it works fine for setuptools before version 8. With setuptools 8 it fails to find any distributions that match this specifier. This stuff was fixed in zc.buildout 2.3.0 with this commit: https://github.com/buildout/buildout/commit/dc32780e7320caed5baf87e2068f693b... BTW, note that pinning zc.recipe.egg in a buildout config would help here. _constrained_requirement_constraint('==1.3.2', requirement) has as result '==1.3.2'. I also wondered why zc.buildout was not getting upgraded. Of course first the current bootstrap.py gets zc.buildout<2dev, so you get zc.buildout 1.7.1. Then when running buildout it calls _maybe_upgrade and this has a check to prevent upgrading to 2.x unless a specific version is requested. So: some puzzles (for me at least) solved. Going forward, it would be nice to either backport the mentioned commit to zc.buildout 1.x (not going to happen I guess) or have an updated bootstrap.py for 1.x that restricts setuptools<8dev. But as said earlier, for projects that do not require zc.buildout 1.x, the latest bootstrap from https://bootstrap.pypa.io should be fine. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl
participants (4)
-
Marius Gedminas -
Maurits van Rees -
Tres Seaver -
Zope tests summarizer