* Coverage per directory
@ 2007-04-25 17:04 Kris Van Hees
2007-04-25 17:06 ` Phil Muldoon
0 siblings, 1 reply; 5+ messages in thread
From: Kris Van Hees @ 2007-04-25 17:04 UTC (permalink / raw)
To: frysk
As a preliminary result in getting more details on the coverage data,
here is a breakdown per directory of executed code lines vs total code
lines. I also list the number of source code files found per directory.
Note that some files are counted twice because they are compiled twice
(once for 32-bit and once for 64-bit).
frysk-core : 8 / 10 ( 80.0000%) ( 1 files)
frysk-core/frysk/bindir : 170 / 525 ( 32.3810%) ( 11 files)
frysk-core/frysk/cli/hpd : 456 / 2507 ( 18.1891%) ( 29 files)
frysk-core/frysk/core : 62 / 63 ( 98.4127%) ( 1 files)
frysk-core/frysk/dom : 434 / 853 ( 50.8792%) ( 13 files)
frysk-core/frysk/dom/cparser : 0 / 550 ( 0.0000%) ( 5 files)
frysk-core/frysk/event : 476 / 514 ( 92.6070%) ( 12 files)
frysk-core/frysk/expr : 0 / 2835 ( 0.0000%) ( 4 files)
frysk-core/frysk/model : 0 / 56 ( 0.0000%) ( 56 files)
frysk-core/frysk/pkglibdir : 310 / 2889 ( 10.7304%) ( 77 files)
frysk-core/frysk/proc : 5196 / 6772 ( 76.7277%) (103 files)
frysk-core/frysk/proc/corefile : 133 / 145 ( 91.7241%) ( 2 files)
frysk-core/frysk/proc/ptrace : 121 / 144 ( 84.0278%) ( 3 files)
frysk-core/frysk/rt : 742 / 2147 ( 34.5599%) ( 22 files)
frysk-core/frysk/rt/states : 30 / 110 ( 27.2727%) ( 11 files)
frysk-core/frysk/util : 178 / 1096 ( 16.2409%) ( 13 files)
frysk-core/frysk/value : 636 / 944 ( 67.3729%) ( 13 files)
frysk-core/prog/kill : 0 / 144 ( 0.0000%) ( 3 files)
frysk-core/prog/perf : 0 / 83 ( 0.0000%) ( 2 files)
frysk-core/prog/step : 0 / 13 ( 0.0000%) ( 1 files)
frysk-core/prog/terminated : 0 / 2 ( 0.0000%) ( 1 files)
frysk-core/prog/util : 0 / 10 ( 0.0000%) ( 1 files)
frysk-gtk : 8 / 10 ( 80.0000%) ( 1 files)
frysk-gtk/EggTrayIcon : 0 / 167 ( 0.0000%) ( 2 files)
frysk-gtk/frysk/gtk : 3 / 4 ( 75.0000%) ( 1 files)
frysk-gtk/org/gnu/gtk/frysk : 2 / 13 ( 15.3846%) ( 1 files)
frysk-gtk/tests/frysk1497 : 20 / 22 ( 90.9091%) ( 2 files)
frysk-gtk/tests/frysk2333 : 20 / 22 ( 90.9091%) ( 1 files)
frysk-gtk/tests/frysk3116 : 21 / 22 ( 95.4545%) ( 1 files)
frysk-gtk/tlwidgets/src/jni : 0 / 262 ( 0.0000%) ( 3 files)
frysk-gtk/tlwidgets/src/widgets : 0 / 2269 ( 0.0000%) ( 4 files)
frysk-gui : 8 / 10 ( 80.0000%) ( 1 files)
frysk-gui/frysk/bindir : 0 / 5 ( 0.0000%) ( 1 files)
frysk-gui/frysk/gui : 48 / 524 ( 9.1603%) ( 7 files)
frysk-gui/frysk/gui/common : 35 / 168 ( 20.8333%) ( 5 files)
frysk-gui/frysk/gui/dialogs : 0 / 215 ( 0.0000%) ( 7 files)
frysk-gui/frysk/gui/disassembler : 0 / 411 ( 0.0000%) ( 3 files)
frysk-gui/frysk/gui/druid : 0 / 412 ( 0.0000%) ( 1 files)
frysk-gui/frysk/gui/memory : 0 / 465 ( 0.0000%) ( 3 files)
frysk-gui/frysk/gui/monitor : 248 / 3105 ( 7.9871%) ( 56 files)
frysk-gui/frysk/gui/monitor/actions : 156 / 401 ( 38.9027%) ( 21 files)
frysk-gui/frysk/gui/monitor/datamodels : 16 / 127 ( 12.5984%) ( 6 files)
frysk-gui/frysk/gui/monitor/eventviewer: 0 / 593 ( 0.0000%) ( 13 files)
frysk-gui/frysk/gui/monitor/filters : 123 / 364 ( 33.7912%) ( 18 files)
frysk-gui/frysk/gui/monitor/observers : 358 / 943 ( 37.9639%) ( 13 files)
frysk-gui/frysk/gui/prefs : 0 / 433 ( 0.0000%) ( 8 files)
frysk-gui/frysk/gui/register : 0 / 362 ( 0.0000%) ( 3 files)
frysk-gui/frysk/gui/sessions : 206 / 516 ( 39.9225%) ( 4 files)
frysk-gui/frysk/gui/srcwin : 0 / 3002 ( 0.0000%) ( 12 files)
frysk-gui/frysk/gui/srcwin/prefs : 0 / 65 ( 0.0000%) ( 3 files)
frysk-gui/frysk/gui/srcwin/tags : 137 / 164 ( 83.5366%) ( 3 files)
frysk-gui/frysk/gui/test : 155 / 321 ( 48.2866%) ( 8 files)
frysk-gui/frysk/vtecli : 0 / 57 ( 0.0000%) ( 1 files)
frysk-imports : 8 / 10 ( 80.0000%) ( 1 files)
frysk-imports/frysk : 76 / 136 ( 55.8824%) ( 3 files)
frysk-imports/frysk/cni : 46 / 48 ( 95.8333%) ( 1 files)
frysk-imports/frysk/expunit : 252 / 290 ( 86.8966%) ( 11 files)
frysk-imports/frysk/imports : 35 / 36 ( 97.2222%) ( 1 files)
frysk-imports/frysk/junit : 165 / 338 ( 48.8166%) ( 4 files)
frysk-imports/frysk/sys : 851 / 1901 ( 44.7659%) ( 36 files)
frysk-imports/frysk/sys/cni : 564 / 963 ( 58.5670%) ( 20 files)
frysk-imports/frysk/sys/proc : 202 / 209 ( 96.6507%) ( 12 files)
frysk-imports/frysk/sys/proc/cni : 208 / 338 ( 61.5385%) ( 8 files)
frysk-imports/frysk/sys/termios : 236 / 257 ( 91.8288%) ( 16 files)
frysk-imports/frysk/sys/termios/cni : 70 / 158 ( 44.3038%) ( 9 files)
frysk-imports/frysk/testbed : 150 / 176 ( 85.2273%) ( 8 files)
frysk-imports/frysk/testbed/cni : 52 / 81 ( 64.1975%) ( 2 files)
frysk-imports/inua/eio : 849 / 1022 ( 83.0724%) ( 19 files)
frysk-imports/inua/eio/cni : 15 / 27 ( 55.5556%) ( 1 files)
frysk-imports/inua/elf : 0 / 129 ( 0.0000%) ( 1 files)
frysk-imports/inua/util : 83 / 243 ( 34.1564%) ( 8 files)
frysk-imports/lib/dw : 296 / 1111 ( 26.6427%) ( 17 files)
frysk-imports/lib/dw/cni : 146 / 404 ( 36.1386%) ( 6 files)
frysk-imports/lib/dw/die : 4 / 448 ( 0.8929%) ( 64 files)
frysk-imports/lib/dw/tests : 62 / 62 (100.0000%) ( 1 files)
frysk-imports/lib/elf : 299 / 744 ( 40.1882%) ( 23 files)
frysk-imports/lib/elf/cni : 172 / 448 ( 38.3929%) ( 9 files)
frysk-imports/lib/elf/tests : 197 / 197 (100.0000%) ( 1 files)
frysk-imports/lib/opcodes : 24 / 44 ( 54.5455%) ( 4 files)
frysk-imports/lib/opcodes/cni : 37 / 49 ( 75.5102%) ( 1 files)
frysk-imports/lib/opcodes/tests : 31 / 42 ( 73.8095%) ( 2 files)
frysk-imports/lib/stdcpp : 17 / 18 ( 94.4444%) ( 2 files)
frysk-imports/lib/stdcpp/cni : 12 / 12 (100.0000%) ( 1 files)
frysk-imports/lib/unwind : 181 / 431 ( 41.9954%) ( 18 files)
frysk-imports/lib/unwind/cni : 121 / 182 ( 66.4835%) ( 4 files)
frysk-imports/tests/audit : 8 / 9 ( 88.8889%) ( 1 files)
frysk-imports/tests/cmdline : 48 / 62 ( 77.4194%) ( 2 files)
frysk-imports/tests/frysk2105 : 10 / 12 ( 83.3333%) ( 2 files)
frysk-imports/tests/frysk2130 : 9 / 18 ( 50.0000%) ( 1 files)
frysk-imports/tests/frysk2270 : 14 / 24 ( 58.3333%) ( 2 files)
frysk-imports/tests/frysk2299 : 94 / 126 ( 74.6032%) ( 1 files)
frysk-imports/tests/frysk2491 : 32 / 35 ( 91.4286%) ( 2 files)
frysk-imports/tests/frysk2493 : 5 / 5 (100.0000%) ( 1 files)
frysk-imports/tests/frysk2595 : 102 / 208 ( 49.0385%) ( 5 files)
frysk-imports/tests/frysk3205 : 14 / 20 ( 70.0000%) ( 1 files)
frysk-imports/tests/frysk3228 : 10 / 11 ( 90.9091%) ( 1 files)
frysk-imports/tests/frysk3231 : 15 / 34 ( 44.1176%) ( 1 files)
frysk-imports/tests/frysk3486 : 42 / 46 ( 91.3043%) ( 1 files)
frysk-imports/tests/frysk3491 : 33 / 43 ( 76.7442%) ( 1 files)
frysk-imports/tests/frysk3525 : 31 / 92 ( 33.6957%) ( 1 files)
frysk-imports/tests/frysk3595 : 15 / 126 ( 11.9048%) ( 1 files)
frysk-imports/tests/frysk3997 : 39 / 67 ( 58.2090%) ( 1 files)
frysk-imports/tests/frysk4217 : 25 / 42 ( 59.5238%) ( 1 files)
frysk-imports/tests/frysk4330 : 21 / 38 ( 55.2632%) ( 1 files)
frysk-imports/tests/process : 96 / 162 ( 59.2593%) ( 4 files)
frysk-imports/tests/vfork-exec : 25 / 60 ( 41.6667%) ( 1 files)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Coverage per directory
2007-04-25 17:04 Coverage per directory Kris Van Hees
@ 2007-04-25 17:06 ` Phil Muldoon
2007-04-25 20:13 ` Phil Muldoon
2007-04-25 20:16 ` Kris Van Hees
0 siblings, 2 replies; 5+ messages in thread
From: Phil Muldoon @ 2007-04-25 17:06 UTC (permalink / raw)
To: Kris Van Hees; +Cc: frysk
Kris Van Hees wrote:
> As a preliminary result in getting more details on the coverage data,
> here is a breakdown per directory of executed code lines vs total code
> lines. I also list the number of source code files found per directory.
> Note that some files are counted twice because they are compiled twice
> (once for 32-bit and once for 64-bit).
>
Because some tests are disabled on some architectures and kernels, it's
always useful to know where the test results originate from. This will
alter test coverage (quite a bit in some cases). It would be good to
establish a baseline (say FC5/x86) and then we could establish testing
deltas for each kernel/architecture from there. I might have missed it
in your original email, but I do not know the architecture and kernel
these tests were run on.
Regards
Phil
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Coverage per directory
2007-04-25 17:06 ` Phil Muldoon
@ 2007-04-25 20:13 ` Phil Muldoon
2007-04-26 20:27 ` Kris Van Hees
2007-04-25 20:16 ` Kris Van Hees
1 sibling, 1 reply; 5+ messages in thread
From: Phil Muldoon @ 2007-04-25 20:13 UTC (permalink / raw)
To: frysk; +Cc: Kris Van Hees
Phil Muldoon wrote:
> Kris Van Hees wrote:
>> As a preliminary result in getting more details on the coverage data,
>> here is a breakdown per directory of executed code lines vs total code
>> lines. I also list the number of source code files found per directory.
>> Note that some files are counted twice because they are compiled twice
>> (once for 32-bit and once for 64-bit).
>>
>
> Because some tests are disabled on some architectures and kernels,
> it's always useful to know where the test results originate from. This
> will alter test coverage (quite a bit in some cases). It would be good
> to establish a baseline (say FC5/x86) and then we could establish
> testing deltas for each kernel/architecture from there. I might have
> missed it in your original email, but I do not know the architecture
> and kernel these tests were run on.
Also, is there a script that given an existing codebase, will run the
tests and provide a report like the one in your email. (Just the tests,
not the full build-scripts you are also working on)?
Regards
Phil
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Coverage per directory
2007-04-25 17:06 ` Phil Muldoon
2007-04-25 20:13 ` Phil Muldoon
@ 2007-04-25 20:16 ` Kris Van Hees
1 sibling, 0 replies; 5+ messages in thread
From: Kris Van Hees @ 2007-04-25 20:16 UTC (permalink / raw)
To: Phil Muldoon; +Cc: Kris Van Hees, frysk
These results are for x86_64 FC6 2.6.20-1.2944.fc6 kernel.
I would love to establish a baseline and collect information across
multiple architectures and kernels, but unfortunately without more
systems being added to the automated build-and-test configuration,
there is a limit to what I can do.
Kris
On Wed, Apr 25, 2007 at 12:03:49PM -0500, Phil Muldoon wrote:
> Kris Van Hees wrote:
> >As a preliminary result in getting more details on the coverage data,
> >here is a breakdown per directory of executed code lines vs total code
> >lines. I also list the number of source code files found per directory.
> >Note that some files are counted twice because they are compiled twice
> >(once for 32-bit and once for 64-bit).
> >
>
> Because some tests are disabled on some architectures and kernels, it's
> always useful to know where the test results originate from. This will
> alter test coverage (quite a bit in some cases). It would be good to
> establish a baseline (say FC5/x86) and then we could establish testing
> deltas for each kernel/architecture from there. I might have missed it
> in your original email, but I do not know the architecture and kernel
> these tests were run on.
>
> Regards
>
> Phil
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Coverage per directory
2007-04-25 20:13 ` Phil Muldoon
@ 2007-04-26 20:27 ` Kris Van Hees
0 siblings, 0 replies; 5+ messages in thread
From: Kris Van Hees @ 2007-04-26 20:27 UTC (permalink / raw)
To: Phil Muldoon; +Cc: frysk, Kris Van Hees
On Wed, Apr 25, 2007 at 12:06:23PM -0500, Phil Muldoon wrote:
> Also, is there a script that given an existing codebase, will run the
> tests and provide a report like the one in your email. (Just the tests,
> not the full build-scripts you are also working on)?
There is no script so far that automates everything beyond the
automated build and test system, and even those have not been released
yet. Right now, building with --enable-coverage works flawlessly, then
running tests with make -k check does a fabulous job. And the missing
piece (parsing all the gcno and gcda files) is being done by a script
that I hope to have availablefor download before end of today. Though
it is still rather a hack.
Kris
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-04-25 20:16 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-04-25 17:04 Coverage per directory Kris Van Hees
2007-04-25 17:06 ` Phil Muldoon
2007-04-25 20:13 ` Phil Muldoon
2007-04-26 20:27 ` Kris Van Hees
2007-04-25 20:16 ` Kris Van Hees
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).