Front page | perl.perl5.porters |
Postings from August 2009
On Wed, Jul 08, 2009 at 09:37:19AM +0200, Paul Johnson wrote: > On Tue, Jul 07, 2009 at 11:18:49PM +0100, Tom Hukins wrote: > > Devel::Cover has failed against maint-5.10 for a few months now. I > > got in touch with Paul, its author, to let him know about this. The > > module's tests fail due to something different that Perl does with its > > code internally (sorry, I don't understand the details) but the module > > itself works fine. > > Yes, a test is failing because the optree has changed somewhat and the > Deparse code I nicked doesn't know about that. I assume that Deparse > itself has been updated so I just need to nick the updated code. > (There's that word again - "just".) The change to the optree was #33710 which was the elsif line number fix for bug #37302 (http://rt.perl.org/rt3//Public/Bug/Display.html?id=37302). The Deparse fix about which I postulated above was change #33714 and I was somewhat surprised to find that I myself was the author of that change. It turns out that the exact same change also fixes Devel::Cover. Why I didn't patch Devel::Cover at the same time, or even remember that I had fixed it in the core is ... er ... um, what was I saying? Aren't airports wonderful places? Airports and hills. Devel::Cover was mostly designed whilst I was cycling up hills. Well, one specific hill, a number of times. And a large number of Devel::Cover's bugs have been fixed in airports. Though recently I haven't been flying as much. Perhaps my gain is Devel::Cover's loss. > I'm not > sure whether I have time to fix up Devel::Cover properly before Dave > gets 5.10.1 out of the door, but I'll make sure that there's a > Devel::Cover available that doesn't fail its tests before that happens, > one way or another. A new version of Devel::Cover (0.65) is heading towards CPAN mirrors as I write this. It has been tested successfully against 5.10.1-RC1, but there are still failures against blead. More on that story later ... -- Paul Johnson - paul@pjcj.net http://www.pjcj.netThread Previous | Thread Next