This is the summary for test reports received on the zope-tests list between 2014-04-04 00:00:00 UTC and 2014-04-05 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 # 596 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / z3c.form_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 winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-April/081639.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/05/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-April/081639.html
On the winbot, where the default charset is ASCII, the doctest failure can't render due to high-order characters: Failure in test c:\buildslave\z3c.form\build\src\z3c\form\browser\README.txt Traceback (most recent call last): File "c:\buildslave\z3c.form\build\bin\test-script.py", line 71, in <module> '--test-path', 'c:\\buildslave\\z3c.form\\build\\src', File "c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\__init__.py", line 27, in run failed = run_internal(defaults, args, script_parts=script_parts, cwd=cwd) File "c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\__init__.py", line 44, in run_internal runner.run() File "c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\runner.py", line 160, in run self.run_tests() File "c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\runner.py", line 242, in run_tests self.skipped, self.import_errors) File "c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\runner.py", line 411, in run_layer import_errors) File "c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\runner.py", line 331, in run_tests test(result) File "c:\Python26_32\lib\unittest.py", line 300, in __call__ return self.run(*args, **kwds) File "c:\Python26_32\lib\unittest.py", line 282, in run result.addFailure(self, self._exc_info()) File "c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\runner.py", line 804, in addFailure exc_info) File "c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\formatter.py", line 348, in test_failure self.print_traceback("Failure in test %s" % test, exc_info) File "c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\formatter.py", line 355, in print_traceback print(self.format_traceback(exc_info)) UnicodeEncodeError: 'ascii' codec can't encode character u'\u2192' in position 863: ordinal not in range(128) On my machine (UTF8), I get super-noisy doctest failures (which I'm not set up to diagnse). One, at least, is probably related to: https://github.com/zopefoundation/z3c.form/commit/c0cbac6f44f88c1434d0f72b95... 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlNAoMoACgkQ+gerLs4ltQ5BlACghK24rWeoaK6AP66OrKS2R0IK SZAAoJYaot2LUQQleJtkpy1gwZb4F4Xt =AuIV -----END PGP SIGNATURE-----
Tres Seaver schreef op 06-04-14 02:33:
"c:\eggs\zope.testrunner-4.4.3-py2.6.egg\zope\testrunner\formatter.py", line 355, in print_traceback print(self.format_traceback(exc_info)) UnicodeEncodeError: 'ascii' codec can't encode character u'\u2192' in position 863: ordinal not in range(128)
This seems due to '→' getting changed to unicode u'\u2192' (→). I guess this only goes wrong when a doctest fails.
On my machine (UTF8), I get super-noisy doctest failures (which I'm not set up to diagnse). One, at least, is probably related to:
https://github.com/zopefoundation/z3c.form/commit/c0cbac6f44f88c1434d0f72b95...
Sorry, my bad. I was in a hurry and forgot to run the tests. I am fixing it now. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl
participants (3)
-
Maurits van Rees -
Tres Seaver -
Zope tests summarizer