[TIP] Coverage.py: Trace function changed
ned at nedbatchelder.com
Thu Dec 6 03:43:11 PST 2012
Tim, last week I posted 3.6b1 to PyPI. I would love to be able to
reproduce the problem you are having. Can I reproduce your test setup?
That is, is it a public repo, and are there clear instructions for how
to configure it and run tests? If not, is there anything unusual in
your code that might affect the trace function?
We can take the detailed debugging offlist.
On 12/6/2012 2:13 AM, Tim Aerdts wrote:
> Untill recently I had very few messages of the following:
> Coverage.py warning: Trace function changed, measurement is likely
> wrong: None
> Up to last week these messages came about twice per test-run. I didn't
> think of it much then. Now last week it started to occur more often
> and now when I run my tests I get the same message 130 times. I
> figured that isn't good.
> I've looked here >
> it is a ticket regarding this but the last person commenting seems to
> have it only when using the pytracer. I have tried switching to the
> pytracer using --timid but it is still the same.
> I might note that I run nosetests --with-coverage and not coverage.py
> Any ideas?
> Kind regards,
> Tim Aerdts
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python