chrism at zope
Sep 27, 2001, 7:23 AM
Post #11 of 18
I don't think it's a well thought-through policy. Maybe this behavior
should be settable via a function in Testing.common that should not be
invoked by default. Additionally, maybe instead of failing with a silly
uninformative message, it could say it failed because a log message above a
certain threshhold was seen.
----- Original Message -----
From: "Jeremy Hylton" <jeremy [at] zope>
To: <chrism [at] zope>
Cc: <jeremy [at] zope>; <evan [at] zope>; <zope-coders [at] zope>
Sent: Thursday, September 27, 2001 10:02 AM
Subject: Re: [Zope-Coders] zLOG warnings and testrunner
> >>>>> "CMcD" == Chris McDonough <chrism [at] digicool> writes:
> CMcD> Jeremy, you might try setting a STUPID_LOG_FILE envvar (no Im
> CMcD> not kidding) to a file, rerun the tests, and see what happens.
> CMcD> I have no idea why pyunit is choking on Zope log calls,
> CMcD> especially because by default nothing actually makes its way
> CMcD> out of Zope without STUPID_LOG_FILE set.
> The Zope Testing.common module installs a log handler that raises an
> AssertionError when a warning or higher is logged. So it's the policy
> of the Zope testing framework, but I've no idea why :-).