[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
>> (Z
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", l
[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--Windo
[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 bra