On Sat, Sep 08, 2012 at 01:00:01AM +0000, Zope tests summarizer wrote: > [2] FAILED winbot / z3c.coverage_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-September/067722.html
This particular error is already fixed (also, it wasn't Windows-specific -- don't we have any Linux buildbots running against the trunks of various packages?); the new one you're going to see tomorrow night is http://winbot.zope.org/builders/z3c.coverage_py_265_32/builds/23/steps/test/logs/stdio and it means "enscript.exe is not in installed or not in %PATH% on winbot". I see three options: (1) have someone find a Windows version of enscript and install it on winbot (2) switch z3c.coverage to use pygments instead of enscript for syntax highlighting (3) skip that particular test if enscript is not available in $PATH Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
signature.asc
Description: Digital signature
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
