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
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