Paul Johnson wrote:
There does seem to be something rather strange going on here. The results for
the unshift a few lines earlier are also duplicated.
Yes, I noticed that after the OP.
But more stragely, the
statement counts on lines 109 and 124 seem somewhat excessive.
My best guess is that some coverage database merging has gone awry. Does that
sound plausible? If you delete all the coverage information and start from
scratch does that "solve" the problem?
I am going to try that now. I have tarred up the structure folder from
the run in question and am going to rerun my program without any
updating from the repository.
Did the runs take place on different
machines?
No.
Are the clocks accurate wherever the runs were executed?
This is the same Linux VM that I've been using since late 2005 in
general and for coverage analysis in Parrot since early 2007. So I have
no reason to expect inaccuracies.
Did you
> get any other messages from Devel::Cover?
Because running coverage takes a long time and the weakest link is my
home wireless connection, I almost always run this in a screen session,
and I've never had reason to record the screen.
If the problem can be reproduced,
is there some way I could reproduce it myself?
I'll send you that tarball of structure/ off list. It's probably too
big to bother other people on list with.
Have I asked enough questions?
You'll get to ask more after I do further research. Thanks.
jimk
