[Zope-Coders] zLOG warnings and testrunner

[Chris McDonough]

Jeremy, you might try setting a STUPID_LOG_FILE envvar (no Im not 
kidding) to a file, rerun the tests, and see what happens.  I have no 
idea why pyunit is choking on Zope log calls, especially because by 
default nothing actually makes its way out of Zope without 
STUPID_LOG_FILE set.

Jeremy Hylton wrote:
> There of the test failures in the Zope suite are caused by warnings
> logged by FileStorage.  Two of the three are tests that I added
> recently; they verify that a storage can be loaded even if the index
> file is corrupted.
> 
> I don't want these tests to fail, because the code works.  I'm not
> sure whether I should change the log level or if there is something
> wrong with the test framework.
> 
> The current FileStorage code logs a warning/problem `if the index file
> is corrupted.  I chose warning because the description of it in
> zLOG/__init__.py seemed to match:  "This isn't causing any immediate
> problems, but deserves attention."  If the index file is corrupted,
> the FileStorage can continue, but the operator ought to know that a
> file was corrupted and check to make sure that there isn't some more
> serious problem.
> 
> Some specific questions:
> 
>     Why does log messages cause tests to fail?
> 
>     When should I use PROBLEM and higher severity levels with zLOG?
> 
>     Should I use a different severity for the specific corrupted index
>     file messages?
> 
> Jeremy
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Zope-Coders mailing list
> Zope-Coders@zope.org
> http://lists.zope.org/mailman/listinfo/zope-coders
> 


-- 
Chris McDonough                    Zope Corporation
http://www.zope.org             http://www.zope.com
"Killing hundreds of birds with thousands of stones"