This is the summary for test reports received on the zope-tests list between 2016-06-02 00:00:00 UTC and 2016-06-03 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] winbot / ZODB_dev py_270_win32 [2] winbot / ZODB_dev py_270_win64 [3] winbot / ZODB_dev py_330_win32 [4] winbot / ZODB_dev py_330_win64 [5] winbot / ZODB_dev py_340_win32 [6] winbot / ZODB_dev py_340_win64 [7] winbot / z3c.batching_py_330_win32 [8] winbot / z3c.batching_py_330_win64 [9] winbot / z3c.breadcrumb_py_330_win32 [10] winbot / z3c.breadcrumb_py_330_win64 [11] winbot / z3c.coverage_py_330_win32 [12] winbot / z3c.coverage_py_330_win64 [13] winbot / z3c.form_py_330_win32 [14] winbot / z3c.form_py_330_win64 [15] winbot / z3c.form_py_340_win32 [16] winbot / z3c.form_py_340_win64 [17] winbot / z3c.formui_py_330_win32 [18] winbot / z3c.formui_py_330_win64 [19] winbot / z3c.layer.ready2go_py_330_win32 [20] winbot / z3c.layer.ready2go_py_330_win64 [21] winbot / z3c.macro_py_330_win32 [22] winbot / z3c.macro_py_330_win64 [23] winbot / z3c.pagelet_py_330_win32 [24] winbot / z3c.pagelet_py_330_win64 [25] winbot / z3c.pagelet_py_340_win32 [26] winbot / z3c.pagelet_py_340_win64 [27] winbot / z3c.table_py_330_win32 [28] winbot / z3c.table_py_330_win64 [29] winbot / z3c.table_py_340_win32 [30] winbot / z3c.table_py_340_win64 [31] winbot / z3c.testing_py_330_win32 [32] winbot / z3c.testing_py_330_win64 [33] winbot / zc.lockfile_py_330_win64 [34] winbot / zope.app.appsetup_py_270_win32 [35] winbot / zope.app.appsetup_py_270_win64 [36] winbot / zope.component_py_340_win32 [37] winbot / zope.component_py_340_win64 [38] winbot / zope.publisher_py_330_win32 [39] winbot / zope.publisher_py_330_win64 [40] winbot / zope.publisher_py_340_win32 [41] winbot / zope.publisher_py_340_win64 [42] winbot / zope.security_py_330_win64 [43] winbot / zope.security_py_340_win64 [44] winbot / zope.sendmail_py_340_win64 [45] winbot / zope.testbrowser_py_330_win32 [46] winbot / zope.testbrowser_py_330_win64 [47] winbot / zope.testing_py_330_win32 [48] winbot / zope.testing_py_330_win64 [49] winbot / zope.testing_py_340_win32 [50] winbot / zope.testing_py_340_win64 [51] winbot / ztk_dev py_270_win32 [52] winbot / ztk_dev py_270_win32 [53] winbot / ztk_dev py_270_win32 [54] winbot / ztk_dev py_270_win32 [55] winbot / ztk_dev py_270_win64 [56] winbot / ztk_dev py_330_win32 [57] winbot / ztk_dev py_330_win32 [58] winbot / ztk_dev py_330_win32 [59] winbot / ztk_dev py_330_win64 Non-OK results -------------- [1] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095149.html [2] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095150.html [3] FAILED winbot / ZODB_dev py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095151.html [4] FAILED winbot / ZODB_dev py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095152.html [5] FAILED winbot / ZODB_dev py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095153.html [6] FAILED winbot / ZODB_dev py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095154.html [7] FAILED winbot / z3c.batching_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095167.html [8] FAILED winbot / z3c.batching_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095165.html [9] FAILED winbot / z3c.breadcrumb_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095179.html [10] FAILED winbot / z3c.breadcrumb_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095188.html [11] FAILED winbot / z3c.coverage_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095173.html [12] FAILED winbot / z3c.coverage_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095180.html [13] FAILED winbot / z3c.form_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095186.html [14] FAILED winbot / z3c.form_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095174.html [15] FAILED winbot / z3c.form_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095155.html [16] FAILED winbot / z3c.form_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095172.html [17] FAILED winbot / z3c.formui_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095185.html [18] FAILED winbot / z3c.formui_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095158.html [19] FAILED winbot / z3c.layer.ready2go_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095161.html [20] FAILED winbot / z3c.layer.ready2go_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095194.html [21] FAILED winbot / z3c.macro_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095195.html [22] FAILED winbot / z3c.macro_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095163.html [23] FAILED winbot / z3c.pagelet_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095162.html [24] FAILED winbot / z3c.pagelet_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095156.html [25] FAILED winbot / z3c.pagelet_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095178.html [26] FAILED winbot / z3c.pagelet_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095191.html [27] FAILED winbot / z3c.table_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095190.html [28] FAILED winbot / z3c.table_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095183.html [29] FAILED winbot / z3c.table_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095157.html [30] FAILED winbot / z3c.table_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095160.html [31] FAILED winbot / z3c.testing_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095198.html [32] FAILED winbot / z3c.testing_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095166.html [33] FAILED winbot / zc.lockfile_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095196.html [34] FAILED winbot / zope.app.appsetup_py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095192.html [35] FAILED winbot / zope.app.appsetup_py_270_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095170.html [36] FAILED winbot / zope.component_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095181.html [37] FAILED winbot / zope.component_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095159.html [38] FAILED winbot / zope.publisher_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095176.html [39] FAILED winbot / zope.publisher_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095189.html [40] FAILED winbot / zope.publisher_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095187.html [41] FAILED winbot / zope.publisher_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095184.html [42] FAILED winbot / zope.security_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095177.html [43] FAILED winbot / zope.security_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095171.html [44] FAILED winbot / zope.sendmail_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095197.html [45] FAILED winbot / zope.testbrowser_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095164.html [46] FAILED winbot / zope.testbrowser_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095168.html [47] FAILED winbot / zope.testing_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095175.html [48] FAILED winbot / zope.testing_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095169.html [49] FAILED winbot / zope.testing_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095193.html [50] FAILED winbot / zope.testing_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095182.html [51] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095204.html [52] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095203.html [53] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095201.html [54] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095199.html [55] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095205.html [56] FAILED winbot / ztk_dev py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095206.html [57] FAILED winbot / ztk_dev py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095202.html [58] FAILED winbot / ztk_dev py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095200.html [59] FAILED winbot / ztk_dev py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095207.html
On Sat, Jun 04, 2016 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095149.html [2] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095150.html [3] FAILED winbot / ZODB_dev py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095151.html [4] FAILED winbot / ZODB_dev py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095152.html [5] FAILED winbot / ZODB_dev py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095153.html [6] FAILED winbot / ZODB_dev py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095154.html
These look like legitimate test failures to me. (Or perhaps the clock on winbot jumped backwards briefly, I can't tell.)
[7] FAILED winbot / z3c.batching_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095167.html [8] FAILED winbot / z3c.batching_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095165.html
This is very strange: TypeError: Class advice impossible in Python3. Use the @implementer class decorator instead. but the build was fine on Travis one month ago: https://travis-ci.org/zopefoundation/z3c.batching/builds/124460711 Another strange thing is that Travis says This is not an active repository You can activate the repository on your profile, or by clicking the button below which I've done, just in case.
[9] FAILED winbot / z3c.breadcrumb_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095179.html [10] FAILED winbot / z3c.breadcrumb_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095188.html
Tried to compile zope.container 4.0.0a2's extension modules and failed with error: Setup script exited with error: command '"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\cl.exe"' failed with exit status -1073740777 which is clear as mud.
[11] FAILED winbot / z3c.coverage_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095173.html [12] FAILED winbot / z3c.coverage_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095180.html
Looks like a real failure that we cannot see because: UnicodeEncodeError: 'charmap' codec can't encode character '\u0bf2' in position 652: character maps to <undefined> Windows uses an 8-bit encoding (cp1252) like it's 1946 and not 2016, which makes zope.testrunner unable to display certain kinds of tracebacks: https://github.com/zopefoundation/zope.testrunner/issues/18
[13] FAILED winbot / z3c.form_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095186.html [14] FAILED winbot / z3c.form_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095174.html [15] FAILED winbot / z3c.form_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095155.html [16] FAILED winbot / z3c.form_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095172.html [17] FAILED winbot / z3c.formui_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095185.html [18] FAILED winbot / z3c.formui_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095158.html [19] FAILED winbot / z3c.layer.ready2go_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095161.html [20] FAILED winbot / z3c.layer.ready2go_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095194.html [23] FAILED winbot / z3c.pagelet_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095162.html [24] FAILED winbot / z3c.pagelet_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095156.html [25] FAILED winbot / z3c.pagelet_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095178.html [26] FAILED winbot / z3c.pagelet_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095191.html
Failure to build lxml 3.1.0: ERROR: b"'xslt-config' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n" ** make sure the development packages of libxml2 and libxslt are installed ** because winbot doesn't build and upload Python >= 3.3 eggs to PyPI: https://github.com/zopefoundation/zope.wineggbuilder/issues/3 https://github.com/zopefoundation/zope.wineggbuilder/issues/7
[21] FAILED winbot / z3c.macro_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095195.html [22] FAILED winbot / z3c.macro_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095163.html
z3c.pt 2.2.3 uses old-style relative imports, i.e. 'import namespaces' to get z3c.pt.namespaces. This won't work on Python 3.3. This is fixed in z3c.pt 3.0.0a1, but that's not a final release and that's why buildout gets the older, broken one. (Also, this repository also wasn't active on Travis. I activated it.)
[27] FAILED winbot / z3c.table_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095190.html [28] FAILED winbot / z3c.table_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095183.html [29] FAILED winbot / z3c.table_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095157.html [30] FAILED winbot / z3c.table_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095160.html
Uses z3c.batching 2.0.1 which doesn't support Python 3 (despite claiming that it does??).
[31] FAILED winbot / z3c.testing_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095198.html [32] FAILED winbot / z3c.testing_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095166.html
Uses zope.app.publication 3.14.0 that doesn't support Python 3 (old-style three-argument 'raise' statement syntax).
[33] FAILED winbot / zc.lockfile_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095196.html [34] FAILED winbot / zope.app.appsetup_py_270_win32
Temporary setuptools source zip 404 error (because of the race condition described in https://bitbucket.org/pypa/pypi/issues/438#comment-27975355
https://mail.zope.org/pipermail/zope-tests/2016-June/095192.html [35] FAILED winbot / zope.app.appsetup_py_270_win64
Looks like a legitimate test failure: Traceback (most recent call last): File "c:\Python27_64\lib\doctest.py", line 1315, in __run compileflags, 1) in test.globs File "<doctest debug.txt[1]>", line 1, in <module> from zope.app.appsetup import debug File "c:\buildslave\zope.app.appsetup_py_270_win64\build\src\zope\app\appsetup\debug.py", line 23, in <module> import zdaemon.zdoptions ImportError: No module named zdaemon.zdoptions
https://mail.zope.org/pipermail/zope-tests/2016-June/095170.html [36] FAILED winbot / zope.component_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095181.html [37] FAILED winbot / zope.component_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095159.html
Failed to compile zope.hookable: error: Setup script exited with error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\BIN\\cl.exe' failed with exit status -1073740777
[38] FAILED winbot / zope.publisher_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095176.html [39] FAILED winbot / zope.publisher_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095189.html [40] FAILED winbot / zope.publisher_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095187.html [41] FAILED winbot / zope.publisher_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095184.html
Looks like legitimate test failures due to a non-UTF-8 encoding.
[42] FAILED winbot / zope.security_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095177.html [43] FAILED winbot / zope.security_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095171.html
Unexpected 64-bitness: - <security proxied builtins.object instance at 0x0000000000C88610> ? -------- + <security proxied builtins.object instance at 0x00C88610> Probably because it tries to distinguish 32- and 64-bit Pythons by inspecting the size of ctypes.long, forgetting that on 64-bit Windows a C 'long' is 32-bits still. A similar bug was recently fixed in, uh, ZODB? persistent? zope.interface? I don't recall.
[44] FAILED winbot / zope.sendmail_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095197.html
Smells like an undeclared dependency on a 3rd-party module (pywin32): ImportError: No module named 'win32file'
[45] FAILED winbot / zope.testbrowser_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095164.html [46] FAILED winbot / zope.testbrowser_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095168.html
https://github.com/zopefoundation/zope.testbrowser/issues/12 looks like
[47] FAILED winbot / zope.testing_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095175.html [48] FAILED winbot / zope.testing_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095169.html [49] FAILED winbot / zope.testing_py_340_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095193.html [50] FAILED winbot / zope.testing_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095182.html
os.symlink() exists but does not work on Windows: NotImplementedError: CreateSymbolicLink functions not found
[51] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095204.html [52] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095203.html [53] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095201.html [54] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095199.html [55] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095205.html
My regexps blame this on https://github.com/buildout/buildout/issues/217 which was closed a year ago, so I guess we need a newer bootstrap.py?
[56] FAILED winbot / ztk_dev py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095206.html [57] FAILED winbot / ztk_dev py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095202.html [58] FAILED winbot / ztk_dev py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095200.html [59] FAILED winbot / ztk_dev py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095207.html
Probably a different manifestation of the same bootstrap issue, this time with 'getopt' rather than 'email'. HTH, Marius Gedminas -- Those of you thinking that grown men with serious jobs should be above such phrases as "way friendlier" should realise that in the 21st century, adult appropriation of infantilisms is de rigueur, innit? -- Stuart Jeffries
On Jun 4, 2016, at 07:40, Marius Gedminas <marius@gedmin.as> wrote:
[43] FAILED winbot / zope.security_py_340_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095171.html
Unexpected 64-bitness:
- <security proxied builtins.object instance at 0x0000000000C88610> ? -------- + <security proxied builtins.object instance at 0x00C88610>
Probably because it tries to distinguish 32- and 64-bit Pythons by inspecting the size of ctypes.long, forgetting that on 64-bit Windows a C 'long' is 32-bits still. A similar bug was recently fixed in, uh, ZODB? persistent? zope.interface? I don't recall.
I suspect you're thinking of https://github.com/zopefoundation/persistent/issues/38. There it turned out the bug was that the C code was simply returning the wrong type for __hash__ on Py3 (and getting away with it on non-64-bit-Windows). Here (https://github.com/zopefoundation/zope.security/blame/master/src/zope/securi...), it looks like there's simply no accounting for pointer size at all on windows (the length of the address repr is hardcoded to 8 digits when the platform is 'win32': https://github.com/zopefoundation/zope.security/commit/e1d5f7cf375ccdfb8f620...). I worked on the persistent bug, but because the error ended up being in C code, I never had to figure out how best to distinguish the two 'win32' cases in Python...but since this fails in ProxyCTests but passes in ProxyPyTests maybe this is a similar bug in the C extension? Jason
On Sat, Jun 04, 2016 at 03:40:40PM +0300, Marius Gedminas wrote:
[7] FAILED winbot / z3c.batching_py_330_win32 https://mail.zope.org/pipermail/zope-tests/2016-June/095167.html [8] FAILED winbot / z3c.batching_py_330_win64 https://mail.zope.org/pipermail/zope-tests/2016-June/095165.html
This is very strange:
TypeError: Class advice impossible in Python3. Use the @implementer class decorator instead.
but the build was fine on Travis one month ago:
https://travis-ci.org/zopefoundation/z3c.batching/builds/124460711
That would be because Travis uses tox, and tox uses setup.py test, and setup.py test happily returns success after finding and running 0 tests. I've switched tox to use zope.testrunner instead and fixed the Python 3 compatibility problems. Marius Gedminas -- Anything can be made to work if you fiddle with it long enough.
participants (3)
-
Jason Madden -
Marius Gedminas -
Zope tests summarizer