Grokbase Groups Perl qa July 2014
FAQ
In accordance with the terms of my grant from TPF this is the monthly
report for my work on improving Devel::Cover covering May and June 2014.

Actually, it's really only for May. I did some work on Devel::Cover in June,
but I am not charging that to the grant, so the month referred to here is May.

This month I released versions 1.14 and 1.15.

Perls 5.20.0 and 5.21.0 were released this month and, thanks in no small part to
work by Matthew Horsfall, they are both fully supported by Devel::Cover.

The main body of work this month was the merging of the cpancover branch. I
have had cpancover.com up and running for some time now. But it has only been
providing coverage for a fairly small subset of the modules on CPAN.
Naturally, I tried to pick the most interesting modules, but the coverage of
CPAN was minimal.

Since the QA hackathon I have been trying to extend the scope of cpancover to
provide coverage for all of CPAN, and not just for the most recent version. In
this quest I have been aided and assisted by Neil Bowers, Olaf Alders and
others.

The major problem with running Devel::Cover on arbitrary code is an extension of
running arbitrary code. Even if the author of the code has no malicious intent
and made no coding mistakes, there are surely bugs in Devel::Cover which might
cause the coverage run to loop indefinitely or to use up all the memory or cause
other problems.

My initial attempts to solve these problems using things like fork and sleep and
kill and killpg weren't completely successful. (Those CPAN authors are so
crafty!) And, naturally, other people who might be willing to provide machines
on which to run cpancover will want some assurances regarding the resource
usage.

So I looked into using Docker. Running each coverage run in an individual
docker container should allow each instance to be resource constrained and
ultimately completely killed if necessary.

Docker is still reasonably immature, but has recently released version 1 which
has removed the warning not to use it in production. I had problems with the
earlier versions, but each release has made it more solid. The branch containing
this work has been fairly successful and is now merger into the git master.

This has been running on cpancover.com and, although I've still not been able to
work all the way through CPAN, there's a pretty good start at
http://cpancover.com/staging/index.html (Warning, that's quite large now - I
need a better solution than showing all modules on a single page.)

Perhaps more importantly, there's a json file available giving basic coverage
information about the covered modules. This will eventually be used by Neil
Bowers' CPAN dashboard and by MetaCPAN to provide information and create links
to a module's cpancover page. It's also available to anyone else who can think
of a good use. Suggestions, and code, welcome. The json data is available at
http://cpancover.com/staging/cpancover.json

I really want to get this cpancover work to pick up new modules as they are
released. I think the only work left is fixing up the occasional problems that
show up because of docker, providing a better landing page and navigation, and
automating the whole thing.

Other work this month included fixing up some testing failures on *BSD and
Windows and providing better support for 5.20 or, more accurately, 5.21 and
beyond when CGI.pm will be removed from the core.

As usual, there were also some patches applied, pull requests merged, and
other bugs fixed.

From the figures below, you can see that this grant is now very nearly
completed. Within the next few weeks I will finish it up and write a closing
report. If you or your company has contributed to the Perl 5 Core Maintenance
Fund then I would like to offer my sincere thanks for your help in funding this
work and trust that you have found it useful. Dan Wright, the Treasurer of The
Perl Foundation, has recently written about how the fund is now almost depleted.
See http://blogs.perl.org/users/dan_wright/2014/07/p5cmf-needs-some-love.html
If you would like to see the other grantees being able to continue their work
(and there is some excellent work being done) then please consider whether you
or, more likely, your company would be in a position to donate to the Core
Maintenance Fund.


Closed Github tickets:

   89 Allow -coverage default,-pod option to cover

Fixed cpantesters reports:

   http://www.cpantesters.org/cpan/report/a46bcdf6-d089-11e3-9f96-e4d5e82f99b1
   http://www.cpantesters.org/cpan/report/5702f9f0-d060-11e3-9f96-e4d5e82f99b1
   http://www.cpantesters.org/cpan/report/9c61f5b4-d051-11e3-967c-c0cca229d549
   http://www.cpantesters.org/cpan/report/0d662304-d037-11e3-9f96-e4d5e82f99b1
   http://www.cpantesters.org/cpan/report/a8c01340-d010-11e3-9f96-e4d5e82f99b1
   http://www.cpantesters.org/cpan/report/3c1d8874-d0bc-11e3-9f96-e4d5e82f99b1

   ... and many more ...

You can see the commits at https://github.com/pjcj/Devel--Cover/commits/master

Hours worked:

   02.05 3:40
   22.05 2:30
   25.05 3:10
   26.05 2:00
   28.05 2:50
   29.05 3:20
   31.05 7:30

   Total 25:00

Total hours worked on grant: 390:25

--
Paul Johnson - paul@pjcj.net
http://www.pjcj.net

Search Discussions

  • Ricardo Signes at Jul 23, 2014 at 4:46 pm
    * Paul Johnson [2014-07-20T18:59:51]
    Hours worked:

    Total 25:00
    Thanks, Paul, +1!

    --
    rjbs
  • Christian Walde at Jul 24, 2014 at 3:39 pm

    On Mon, 21 Jul 2014 00:59:51 +0200, Paul Johnson wrote:

    http://cpancover.com/staging/index.html (Warning, that's quite large now

    Total 25:00
    That is a hell of a thing. Thanks for your work and +1. :)

    Also, might i suggest posting this email on BPO?

    --
    With regards,
    Christian Walde
  • Gabor Szabo at Aug 1, 2014 at 5:11 am

    On Thu, Jul 24, 2014 at 6:39 PM, Christian Walde wrote:

    On Mon, 21 Jul 2014 00:59:51 +0200, Paul Johnson wrote:

    http://cpancover.com/staging/index.html (Warning, that's quite large now
    Total 25:00
    That is a hell of a thing. Thanks for your work and +1. :)

    Also, might i suggest posting this email on BPO?

    or at least on http://news.perlfoundation.org/ ...

    Gabor
  • Paul Johnson at Aug 1, 2014 at 12:32 pm

    On Fri, Aug 01, 2014 at 08:11:15AM +0300, Gabor Szabo wrote:
    On Thu, Jul 24, 2014 at 6:39 PM, Christian Walde wrote:

    Also, might i suggest posting this email on BPO?
    That's a good point - I should probably have been doing that all along.
    I'll try to remember for the final report. But,
    all the previous reports have ended up there, posted by either Mark or
    Karen. But, as busy folk, it sometimes takes a day or two for that to
    happen. I should probably have explicitly let you know, Gabor, for
    newsletter purposes, but again it's a little late now. Oh well, I'll
    know better for next time ;-)

    --
    Paul Johnson - paul@pjcj.net
    http://www.pjcj.net
  • Christian Walde at Aug 3, 2014 at 7:03 pm

    On Fri, 01 Aug 2014 14:32:44 +0200, Paul Johnson wrote:
    On Fri, Aug 01, 2014 at 08:11:15AM +0300, Gabor Szabo wrote:
    On Thu, Jul 24, 2014 at 6:39 PM, Christian Walde
    <walde.christian@gmail.com>
    wrote:
    Also, might i suggest posting this email on BPO?
    That's a good point - I should probably have been doing that all along.
    Mildly agree, though you had more important things on your mind.
    I'll try to remember for the final report.
    Mildly disagree and think it's still worth it to put the May/June report
    on BPO as well, even if it's a bit after the mail. D::C can benefit from
    ANY publicity. If you don't mind i'll do it for you.

    --
    With regards,
    Christian Walde
  • Paul Johnson at Aug 4, 2014 at 12:48 am

    On Sun, Aug 03, 2014 at 09:02:56PM +0200, Christian Walde wrote:
    On Fri, 01 Aug 2014 14:32:44 +0200, Paul Johnson wrote:

    I'll try to remember for the final report.
    Mildly disagree and think it's still worth it to put the May/June
    report on BPO as well, even if it's a bit after the mail. D::C can
    benefit from ANY publicity. If you don't mind i'll do it for you.
    On Sun, Aug 03, 2014 at 07:49:13AM +0300, Gabor Szabo wrote:
    Thanks, though it is not only for newsletter purposes. There is a feeling
    (at least in me)
    that a blog post, especially on TPF web site is a much more
    serious/official statement than
    an e-mail in a mailing list.
    The terms of my grant are that reports get posted here, but I think you
    are both correct that there is benefit in posting elsewhere too.

    Karen has kindly updated perlfoundation.org
    http://news.perlfoundation.org/2014/08/develcover-grant-report-may-an.html
    and I have posted to blogs.perl.org
    http://blogs.perl.org/users/paul_johnson/2014/08/tpf-develcover-grant-report-mayjune-2014.html

    Thanks for the prompts,

    --
    Paul Johnson - paul@pjcj.net
    http://www.pjcj.net
  • Gabor Szabo at Aug 3, 2014 at 4:49 am
    On Fri, Aug 1, 2014 at 3:32 PM, Paul Johnson wrote:
    all the previous reports have ended up there, posted by either Mark or
    Karen. But, as busy folk, it sometimes takes a day or two for that to
    happen. I should probably have explicitly let you know, Gabor, for
    newsletter purposes, but again it's a little late now. Oh well, I'll
    know better for next time ;-)

    Thanks, though it is not only for newsletter purposes. There is a feeling
    (at least in me)
    that a blog post, especially on TPF web site is a much more
    serious/official statement than
    an e-mail in a mailing list. Besides, I am also collecting all the reports
    of every grant given by TPF
    http://perlmaven.com/tpf (click on the + to see the list) to make it easier
    for people
    to get to the details.


    (I'll probably add the data to the https://github.com/rjbs/tpf-grant-history
    when time permits.)

    regards
        Gabor

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupqa @
categoriesperl
postedJul 20, '14 at 11:00p
activeAug 4, '14 at 12:48a
posts8
users4
websiteqa.perl.org

People

Translate

site design / logo © 2019 Grokbase