On Saturday 09 April 2005 21:20, Tim Peters wrote:
> [Stephan Richter]
> > I have removed all unit test failures when running the test runner with
> > "-N 2",
> Really?  You don't see the new failure I reported here yesterday?
> That's got nothing to do with -N, though:
>     http://mail.zope.org/pipermail/zope3-dev/2005-April/014158.html

I had originally deleted this last test, so they would pass (it was not only 
on Windows), so a simple "svn up" should have sufficed. However, I just 
reenabled the test and fixed it for good.

> > except for one failure in the ZODB tests, since I know nothing about this
> > code.
> This may be hard to fix.  It really has nothing to do with ZODB, it's
> testing that various deprecated methods generate deprecation warnings,
> and the behavior across multiple runs has to do with private internals
> of Python's ``warnings`` module.  The latter tries to avoid showing
> the same msg from the same line twice, and that's exactly what's going
> wrong here:  on the second run the test isn't seeing the warnings it
> saw on its first run ... OK, hacked around that, but Zope3 won't
> notice until I check it in _and_ someone switches Zope3 to use a new

Right, I know about this. Mmh, in fact, it surprises me now that my 
deprecation module doctests do not complain in the second run. It is probably 
one of the advantages of doc file tests, since their module gets regenerated 
for every test run, so that the deprecation framework does not detect the 
warning duplication.

Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to