buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000 zc-bbwin. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2398 Blamelist: efge,sidnei BUILD FAILED: failed test sincerely, -The Buildbot
buildbot@zope.com wrote:
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000 zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes Build Source Stamp: 2398 Blamelist: efge,sidnei
BUILD FAILED: failed test
FYI test output is: C:\WINDOWS\system32\cmd.exe /c c:\python24\python.exe test.py -v -m !^^(ZEO|zope[.]app[.]) --all in dir C:\buildbot\.org\zc-bbwin--Windows 2000--Zope---branches---2.9--2.4\build (timeout 1200 secs) argv: ['C:\\WINDOWS\\system32\\cmd.exe', '/c', 'c:\\python24\\python.exe test.py -v -m !^^(ZEO|zope[.]app[.]) --all'] environment: {'TMP': 'C:\\DOCUME~1\\buildbot\\LOCALS~1\\Temp', 'COMPUTERNAME': 'BBWIN', 'LIB': 'C:\\Program Files\\Microsoft Visual Studio .NET 2003\\SDK\\v1.1\\Lib\\', 'USERDOMAIN': 'BBWIN', 'PYTHON': 'c:\\python24\\python.exe', 'COMMONPROGRAMFILES': 'C:\\Program Files\\Common Files', 'PROCESSOR_IDENTIFIER': 'x86 Family 15 Model 4 Stepping 1, GenuineIntel', 'PROGRAMFILES': 'C:\\Program Files', 'PROCESSOR_REVISION': '0401', 'SYSTEMROOT': 'C:\\WINDOWS', 'PATH': 'C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;c:\\utils;C:\\Program Files\\Subversion\\bin', 'VIM': 'C:\\Program Files\\Vim', 'TEMP': 'C:\\DOCUME~1\\buildbot\\LOCALS~1\\Temp', 'PROCESSOR_ARCHITECTURE': 'x86', 'VS71COMNTOOLS': 'C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Common7\\Tools\\', 'APR_ICONV_PATH': 'C:\\Program Files\\Subversion\\iconv', 'ALLUSERSPROFILE': 'C:\\Documents and Settings\\All Users', 'INSTANCE_HOME': 'C:\\buildbot\\.com\\bbwin--Windows--FIPS-1---trunk--2.4\\build\\instance', 'SESSIONNAME': 'Console', 'HOMEPATH': '\\Documents and Settings\\buildbot', 'USERNAME': 'buildbot', 'LOGONSERVER': '\\\\BBWIN', 'PROMPT': '$P$G', 'COMSPEC': 'C:\\WINDOWS\\system32\\cmd.exe', 'PATHEXT': '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH', 'INCLUDE': 'C:\\Program Files\\Microsoft Visual Studio .NET 2003\\SDK\\v1.1\\include\\', 'FP_NO_HOST_CHECK': 'NO', 'WINDIR': 'C:\\WINDOWS', 'HOMEDRIVE': 'C:', 'APPDATA': 'C:\\Documents and Settings\\buildbot\\Application Data', 'SYSTEMDRIVE': 'C:', 'NUMBER_OF_PROCESSORS': '1', 'SVN_SSH': 'c:/putty/plink.exe', 'PROCESSOR_LEVEL': '15', 'OS': 'Windows_NT', 'USERPROFILE': 'C:\\Documents and Settings\\buildbot'} 'zope[.]app[.])' is not recognized as an internal or external command, operable program or batch file. program finished with exit code 255 Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg@nuxeo.com
[Florent Guillaume]
FYI test output is: ... 'zope[.]app[.])' is not recognized as an internal or external command, operable program or batch file. program finished with exit code 255
That was due to an ill-formed command line, which Jim repaired this morning. Zope trunk and Zope 2.9 branch are still failing on Windows, though, with different symptoms now: """ Failure in test test_checkPermission_proxy_role_scope (AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests) Traceback (most recent call last): File "c:\python24\lib\unittest.py", line 260, in run testMethod() File "C:\buildbot\.org\zc-bbwin--Windows 2000--Zope---trunk--2.4\build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py", line 326, in test_checkPermission_proxy_role_scope self.failUnless(self.policy.checkPermission('Kill', r_subitem, context)) File "c:\python24\lib\unittest.py", line 309, in failUnless if not expr: raise self.failureException, msg AssertionError . Failure in test test_checkPermission_proxy_roles_limit_access (AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests) Traceback (most recent call last): File "c:\python24\lib\unittest.py", line 260, in run testMethod() File "C:\buildbot\.org\zc-bbwin--Windows 2000--Zope---trunk--2.4\build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py", line 302, in test_checkPermission_proxy_roles_limit_access self.failIf(self.policy.checkPermission('Foo', r_item, context)) File "c:\python24\lib\unittest.py", line 305, in failIf if expr: raise self.failureException, msg AssertionError . Failure in test test_checkPermission_respects_proxy_roles (AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests) Traceback (most recent call last): File "c:\python24\lib\unittest.py", line 260, in run testMethod() File "C:\buildbot\.org\zc-bbwin--Windows 2000--Zope---trunk--2.4\build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py", line 291, in test_checkPermission_respects_proxy_roles self.failUnless(self.policy.checkPermission('View', r_item, context)) File "c:\python24\lib\unittest.py", line 309, in failUnless if not expr: raise self.failureException, msg AssertionError """ I don't have time to look at it. Since the Windows buildbot slave `bbwin` doesn't have a C compiler, I suppose it's possible that the old, canned .pyd files it uses are out of synch with the current C code.
[Tim Peters]
... Failure in test test_checkPermission_proxy_roles_limit_access (AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests) Traceback (most recent call last): File "c:\python24\lib\unittest.py", line 260, in run testMethod() File "C:\buildbot\.org\zc-bbwin--Windows2000--Zope---trunk--2.4\build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py", line 302, in test_checkPermission_proxy_roles_limit_access self.failIf(self.policy.checkPermission('Foo', r_item, context)) File "c:\python24\lib\unittest.py", line 305, in failIf if expr: raise self.failureException, msg AssertionError ... I don't have time to look at it. Since the Windows buildbot slave `bbwin` doesn't have a C compiler, I suppose it's possible that the old, canned .pyd files it uses are out of synch with the current C code.
That was the problem. Turns out `bbwin` does have a compiler, but the buildbot recipe didn't use it. After Jim fixed that, we have another Windows-specific failure, in new code from ChrisM (this is on Zope trunk, of course): Failure in test test_get_env (ZServer.tests.test_clockserver.ClockServerTests) Traceback (most recent call last): File "c:\python24\lib\unittest.py", line 260, in run testMethod() File "C:\buildbot\.org\zc-bbwin--Windows 2000--Zope---trunk--2.4\build\lib\python\ZServer\tests\test_clockserver.py", line 87, in test_get_env self.assertEqual(env['PATH_TRANSLATED'], '/a /b') File "c:\python24\lib\unittest.py", line 333, in failUnlessEqual raise self.failureException, \ AssertionError: '\\a \\b' != '/a /b'
Hmmm... I *think* I just fixed this. On Dec 21, 2005, at 3:48 PM, Tim Peters wrote:
[Tim Peters]
... Failure in test test_checkPermission_proxy_roles_limit_access (AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests) Traceback (most recent call last): File "c:\python24\lib\unittest.py", line 260, in run testMethod() File "C:\buildbot\.org\zc-bbwin--Windows2000--Zope---trunk--2.4 \build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py", line 302, in test_checkPermission_proxy_roles_limit_access self.failIf(self.policy.checkPermission('Foo', r_item, context)) File "c:\python24\lib\unittest.py", line 305, in failIf if expr: raise self.failureException, msg AssertionError ... I don't have time to look at it. Since the Windows buildbot slave `bbwin` doesn't have a C compiler, I suppose it's possible that the old, canned .pyd files it uses are out of synch with the current C code.
That was the problem. Turns out `bbwin` does have a compiler, but the buildbot recipe didn't use it. After Jim fixed that, we have another Windows-specific failure, in new code from ChrisM (this is on Zope trunk, of course):
Failure in test test_get_env (ZServer.tests.test_clockserver.ClockServerTests) Traceback (most recent call last): File "c:\python24\lib\unittest.py", line 260, in run testMethod() File "C:\buildbot\.org\zc-bbwin--Windows 2000--Zope---trunk--2.4\build\lib\python\ZServer\tests \test_clockserver.py", line 87, in test_get_env self.assertEqual(env['PATH_TRANSLATED'], '/a /b') File "c:\python24\lib\unittest.py", line 333, in failUnlessEqual raise self.failureException, \ AssertionError: '\\a \\b' != '/a /b'
[Tim Peters]
... That was the problem. Turns out `bbwin` does have a compiler, but the buildbot recipe didn't use it. After Jim fixed that, we have another Windows-specific failure, in new code from ChrisM (this is on Zope trunk, of course):
Failure in test test_get_env (ZServer.tests.test_clockserver.ClockServerTests) Traceback (most recent call last): File "c:\python24\lib\unittest.py", line 260, in run testMethod() File "C:\buildbot\.org\zc-bbwin--Windows 2000--Zope---trunk--2.4\build\lib\python\ZServer\tests \test_clockserver.py", line 87, in test_get_env self.assertEqual(env['PATH_TRANSLATED'], '/a /b') File "c:\python24\lib\unittest.py", line 333, in failUnlessEqual raise self.failureException, \ AssertionError: '\\a \\b' != '/a /b'
[Chris McDonough]
Hmmm... I *think* I just fixed this.
Luckily for us, the buildbot doesn't give a rip what either of us think. Its judgment is that you _did_ fix it, and there's not a court in the land that will convict you given that perfect defense.
participants (4)
-
buildbot＠zope.com -
Chris McDonough -
Florent Guillaume -
Tim Peters