Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin
[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. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin
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' ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin
[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' ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin
[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. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )