zope-tests - FAILED: 7, OK: 6
This is the summary for test reports received on the zope-tests list between 2013-07-10 00:00:00 UTC and 2013-07-11 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 # 325 [1] winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 [3] winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 [5] winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [6] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [7] winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077783.html [2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077784.html [3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077785.html [4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077786.html [5] FAILED winbot / ztk_10 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077777.html [6] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077780.html [7] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077782.html
On Fri, Jul 12, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
This is the summary for test reports received on the zope-tests list between 2013-07-10 00:00:00 UTC and 2013-07-11 00:00:00 UTC:
It's great to see these back! Well, not the failures, but you know what I mean.
[1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077783.html
This is an interesting one: Error in test test_funky_datetime_serialization (ZODB.tests.testSerialize.SerializerFunctestCase) Traceback (most recent call last): File "c:\Python26_32\lib\unittest.py", line 279, in run testMethod() File "c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\tests\testSerialize.py", line 143, in test_funky_datetime_serialization subprocess.check_call(prep_args, env=environ) File "c:\Python26_32\lib\subprocess.py", line 488, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command '['c:\\Python26_32\\python.exe', '-c', 'from ZODB.tests.testSerialize import _functest_prep; _functest_prep("c:\\buildslave\\ZODB_dev_py_265_win32\\build\\parts\\test\\tmp\\tmpvz2yhtserializerfunc\\Data.fs")']' returned non-zero exit status 1 'import site' failed; use -v for traceback Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: No module named ZODB.tests.testSerialize Looks like the subprocess is being run with the wrong interpreter or environment. The code looks like this: prep_args = [sys.executable, '-c', 'from ZODB.tests.testSerialize import _functest_prep; ' '_functest_prep("%s")' % fqn] # buildout doesn't arrange for the sys.path to be exported, # so force it ourselves environ = os.environ.copy() environ['PYTHONPATH'] = ':'.join(sys.path) subprocess.check_call(prep_args, env=environ) Hmm. I cannot reproduce the error on Linux. Heyyy, doesn't Windows use semicolons to separate path components? Use os.pathsep, Luke! Committed in d11576d.
[2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077784.html
Curiously enough, a different error -- while running buildout: Traceback (most recent call last): File "c:\buildslave\ZODB_dev_py_265_win64\build\bin\buildout-script.py", line 15, in <module> import site # imports custom buildout-generated site.py File "c:\buildslave\ZODB_dev_py_265_win64\build\parts\buildout\site.py", line 558, in <module> main() File "c:\buildslave\ZODB_dev_py_265_win64\build\parts\buildout\site.py", line 541, in main known_paths = addsitepackages(known_paths) File "c:\buildslave\ZODB_dev_py_265_win64\build\parts\buildout\site.py", line 262, in addsitepackages import pkg_resources ImportError: No module named pkg_resources I've no clue. I've randomly updated ZODB's bootstrap.py to the latest version to see if it has any effect on this.
[3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-July/077785.html
Another new error: Traceback (most recent call last): File "c:\Python27_32\lib\site.py", line 549, in <module> main() File "c:\Python27_32\lib\site.py", line 525, in main known_paths = removeduppaths() File "c:\Python27_32\lib\site.py", line 105, in removeduppaths dir, dircase = makepath(dir) File "c:\Python27_32\lib\site.py", line 79, in makepath dir = os.path.abspath(os.path.join(*paths)) File "c:\Python27_32\lib\ntpath.py", line 465, in abspath path = _getfullpathname(path) TypeError: must be (buffer overflow), not str I don't even. This is probably related to that "'import site' failed; use -v for traceback" we saw before, in [1]. It is followed by Error in test test_funky_datetime_serialization (ZODB.tests.testSerialize.SerializerFunctestCase) Traceback (most recent call last): File "c:\Python27_32\lib\unittest\case.py", line 318, in run testMethod() File "c:\buildslave\zodb_dev_py_270_win32\build\src\ZODB\tests\testSerialize.py", line 143, in test_funky_datetime_serialization subprocess.check_call(prep_args, env=environ) File "c:\Python27_32\lib\subprocess.py", line 504, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command '['c:\\Python27_32\\python.exe', '-c', 'from ZODB.tests.testSerialize import _functest_prep; _functest_prep("c:\\buildslave\\ZODB_dev_py_270_win32\\build\\parts\\test\\tmp\\tmpxkxjyjserializerfunc\\Data.fs")']' returned non-zero exit status 1 which is similar. I'm hoping d11576d will fix this one as well.
[4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077786.html
Same as [2] -- ImportError: No module named pkg_resources
[5] FAILED winbot / ztk_10 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077777.html
[6] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077780.html
[7] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077782.html
All on Win64, all fail with ImportError: No module named pkg_resources in buildout Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer