Re: 'master' 'make check' lcov code coverage report

On Mon, Nov 3, 2014 at 6:09 PM, Markus Mohrhard <
markus.mohrhard@googlemail.com> wrote:
> Hey Maarten,
>
> On Mon, Nov 3, 2014 at 4:10 PM, Caolán McNamara <caolanm@redhat.com>
wrote:
> > On Mon, 2014-11-03 at 12:44 +0100, Maarten Hoes wrote:
> > > Hi,
> > > I ran an gcov/lcov report of 'make check' on master
> > > ('sccomp_lpsolver.test' and 'sw_tox.test' failed for some reason with
> > > a core dump, and therefore are excluded from the results), which I
> > > could (if interested) upload (if given access) to
> > > dev-builds.libreoffice.org/lcov_reports/ for comparison with the
> > > report generated for master on 11-Apr-2014.
> >
> > Maybe cloph or moggi could sort our some type of access there. I'd be
> > interested especially interested in which dirs in
> > filter/source/graphicfilter have 0 coverage and are import filters.
>
> That is in general no problem. Just send your public ssh key to cloph.
public key is mailed.

> In general I think it makes sense to move that to one of the TDF VMs
> and implement a script similar to the coverity one that is more or
> less run once a week.
Looking briefly at the differences (or lack thereof) in the reports of both
11-Apr-2014 and today, I cannot help but wonder if running the report as
often as weekly would be beneficial at this point. Doing it manually once
every few months seems often enough for now ? Of course, I would be glad to
be wrong here.
;)

> If you are interested in working on that we can
> surely work something out to get you access to one of the VMs to
> automated the generation of the reports.
If bourne/korn shell is considered acceptable, Im willing to try to hack up
a script that runs a git pull/lcov report and scp uploads the results
somewhere. If it needs to be written in something else (buildbot, python,
whatever) I may not be the best man for the job. However, I was able to
generate the report quite easily by following the guidelines for it in the
wiki, so it shouldnt be too hard to do for someone that is able to write a
script for it in other languages I guess.



- Maarten