[TIP] Coverage.py: Trace function changed
fragger123 at gmail.com
Thu Dec 6 03:49:13 PST 2012
Taking this offlist with Ned, will post back once a solution has been found.
On Thu, Dec 6, 2012 at 12:43 PM, Ned Batchelder <ned at nedbatchelder.com>wrote:
> 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
> I've looked here >
> https://bitbucket.org/ned/coveragepy/issue/164/trace-function-changed-warning-when-usingit 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 listtesting-in-python at lists.idyll.orghttp://lists.idyll.org/listinfo/testing-in-python
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python