Hi Dean,
Croc (the coverage utility) currently takes an expansive view of which files
need to be covered. That's to catch cases where a new source file is added,
but not compiled into any tests.
The rules which Croc uses on linux are a combination of those in
src/build/common.croc and src/build/linux/chrome_linux.croc. We can add
exclusions to those rules as needed to fix cases like these. For example,
the following rule will exclude .../wmi_util.*
{
'regexp' : '.*/(wmi_util)\.',
'include' : 0,
},
- Randall
2009/6/3 Dean McNamee <[email protected]>
> Seems there are some bugs relating to which files count. For example:
>
>
> http://build.chromium.org/buildbot/coverage/linux-debug/17471/CHROMIUM/base/index.html
>
> It counts files like wmi_util, which is Windows specific and not
> compiled on Linux.
>
> On Wed, Jun 3, 2009 at 9:12 PM, Paweł Hajdan Jr.<[email protected]>
> wrote:
> >
> > Looks cool! I wonder... what does "instrumented, but not executed"
> > (yellow) mean?
> >
> > On Wed, Jun 3, 2009 at 18:31, Randall Spangler <[email protected]>
> wrote:
> >> The Chromium code coverage dashboard is now live!
> >>
> >> View it here: http://build.chromium.org/buildbot/coverage/
> >> ...or click on the 'coverage' link at the top of the main
> >> http://build.chromium.org waterfall, right next to the 'perf' link.
> >>
> >> This dashboard reports code coverage statistics on Chromium on each
> platform
> >> - that is, which lines of code are executed by unit tests. It's one
> measure
> >> of how comprehensive the tests are, and helps identify tests which
> aren't
> >> running and source code which has excaped testing.
> >>
> >> The top-level dashboard reports the following:
> >>
> >> Percent coverage for source code (excluding tests) - that is, what we
> want
> >> to test.
> >> Percent coverage for the tests themselves. The low numbers here
> indicate
> >> that not all the tests are currently running under coverage. This
> should
> >> approach 100%.
> >>
> >> If you click through on a graph, you get a full-page view of the graph
> where
> >> you can click on an individual data point to get more details on that
> build.
> >>
> >> CL = details on the changelists for that build (you're seen this before
> on
> >> other perf graphs..)
> >> Coverage = detailed coverage data on all subdirectories and files, down
> to
> >> line-by-line coverage (this is new!)
> >>
> >> Coverage runs nightly on linux and mac platforms and currently covers
> only
> >> the base/net/media/printing submodules.
> >>
> >> The builds are on the right side of the experimental dashboard
> >> (http://build.chromium.org/buildbot/waterfall.fyi)
> >>
> >> Coming soon: windows platform, test_shell, more submodules, etc.
> >>
> >> (Thanks to jrg for getting unit tests running under coverage, and
> nsylvain
> >> for helping me with buildbot.)
> >>
> >> - Randall
> >> [email protected]
> >>
> >>
> >> >
> >>
> >
> > > >
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
