From: "Nick Yin" <nickyin@hotmail.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: some udev code coverage results
Date: Tue, 27 Apr 2004 01:03:58 +0000 [thread overview]
Message-ID: <BAY7-F8xQcNuJsG92lJ0000ffaf@hotmail.com> (raw)
In-Reply-To: <1083019150.26612.148.camel@ibm-d.pdx.osdl.net>
Hi,
How about your coverage for the whole udev project? I have got a coverage
data 86.8% for the whole project by our test suite. How do you think of this
result?
In addition, there is no coverage data for udevd.c, you can test it using
test/udevd/udevd-test.pl in udev-025 or later version:-)
Thanks!
Nick
>From: Leann Ogasawara <ogasawara@osdl.org>
>To: hotplug <linux-hotplug-devel@lists.sourceforge.net>
>CC: Greg KH <greg@kroah.com>, Mary Edie <maryedie@osdl.org>
>Subject: some udev code coverage results
>Date: Mon, 26 Apr 2004 15:39:10 -0700
>
>Hi All,
>
>Some people have asked how the code coverage for udev looked. I ran
>gcov for udev on all the tests in udev/test/ and received the following
>results (which are enclosed below and also at the link listed):
>
>http://developer.osdl.org/ogasawara/gcov_for_udev/testall_udev_gcov.txt
>
>Thanks,
>
>Leann
>
>CODE COVERAGE ANALYSIS FOR UDEV
>
>################
>udev.c
>################
>100.00% of 3 source lines executed in file logging.h
>Creating udev.c.logging.h.gcov.
> 79.66% of 59 source lines executed in file udev.c
>Creating udev.c.gcov.
>
>################
>udev_lib.c
>################
>100.00% of 15 source lines executed in file list.h
>Creating udev_lib.c.list.h.gcov.
> 80.39% of 102 source lines executed in file udev_lib.c
>Creating udev_lib.c.gcov.
>
>################
>udev_config.c
>################
> 93.07% of 101 source lines executed in file udev_config.c
>Creating udev_config.c.gcov.
>
>################
>udev-add.c
>################
> 78.83% of 222 source lines executed in file udev-add.c
>Creating udev-add.c.gcov.
>
>################
>udev-remove.c
>################
> 95.83% of 72 source lines executed in file udev-remove.c
>Creating udev-remove.c.gcov.
>
>################
>udevdb.c
>################
> 44.94% of 89 source lines executed in file udevdb.c
>Creating udevdb.c.gcov.
>
>################
>namedev.c
>################
>100.00% of 1 source lines executed in file list.h
>Creating namedev.c.list.h.gcov.
> 89.51% of 429 source lines executed in file namedev.c
>Creating namedev.c.gcov.
>
>################
>namedev_parse.c
>################
>100.00% of 8 source lines executed in file list.h
>Creating namedev_parse.c.list.h.gcov.
> 92.42% of 211 source lines executed in file namedev_parse.c
>Creating namedev_parse.c.gcov.
>
>################
>dev_d.c
>################
> 95.45% of 44 source lines executed in file dev_d.c
>Creating dev_d.c.gcov.
>
>################
>sysfs_bus.c
>################
> 0.00% of 2 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs/libsysfs.h
>Creating sysfs_bus.c.libsysfs.h.gcov.
> 0.00% of 182 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs_bus.c
>Creating sysfs_bus.c.gcov.
>
>################
>sysfs_class.c
>################
> 0.00% of 2 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs/libsysfs.h
>Creating sysfs_class.c.libsysfs.h.gcov.
> 34.74% of 308 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs_class.c
>Creating sysfs_class.c.gcov.
>
>################
>sysfs_device.c
>################
> 0.00% of 2 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs/libsysfs.h
>Creating sysfs_device.c.libsysfs.h.gcov.
> 39.74% of 312 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs_device.c
>Creating sysfs_device.c.gcov.
>
>################
>sysfs_dir.c
>################
>100.00% of 2 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs/libsysfs.h
>Creating sysfs_dir.c.libsysfs.h.gcov.
> 43.12% of 494 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs_dir.c
>Creating sysfs_dir.c.gcov.
>
>################
>sysfs_driver.c
>################
> 0.00% of 2 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs/libsysfs.h
>Creating sysfs_driver.c.libsysfs.h.gcov.
> 0.00% of 170 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs_driver.c
>Creating sysfs_driver.c.gcov.
>
>################
>sysfs_utils.c
>################
> 57.02% of 228 source lines executed in file
>/home/ogasawara/udev/libsysfs/sysfs_utils.c
>Creating sysfs_utils.c.gcov.
>
>################
>dlist.c
>################
> 68.94% of 132 source lines executed in file
>/home/ogasawara/udev/libsysfs/dlist.c
>Creating dlist.c.gcov.
>
>################
>tdb.c
>################
> 42.12% of 964 source lines executed in file tdb/tdb.c
>Creating tdb.c.gcov.
>
>################
>spinlock.c
>################
> 66.67% of 9 source lines executed in file tdb/spinlock.c
>Creating spinlock.c.gcov.
>
>################
>udevsend.c
>################
> 81.48% of 81 source lines executed in file udevsend.c
>Creating udevsend.c.gcov.
>
>################
>udevd.c
>################
>code for udevd.c was never executed
>no code coverage analysis to be done
>
>################
>udevinfo.c
>################
>code for udevinfo.c was never executed
>no code coverage analysis to be done
>
>################
>udevtest.c
>################
> 82.86% of 35 source lines executed in file udevtest.c
>Creating udevtest.c.gcov.
>
>################
>udevstart.c
>################
>code for udevstart.c was never executed
>no code coverage analysis to be done
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
>For a limited time only, get FREE Ground shipping on all orders of $35
>or more. Hurry up and shop folks, this offer expires April 30th!
>http://www.thinkgeek.com/freeshipping/?cpg\x12297
>_______________________________________________
>Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
>Linux-hotplug-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
http://join.msn.com/?pageþatures/virus
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-04-27 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 22:39 some udev code coverage results Leann Ogasawara
2004-04-27 1:03 ` Nick Yin [this message]
2004-04-27 16:34 ` Leann Ogasawara
2004-04-27 16:43 ` Greg KH
2004-04-28 0:56 ` Nick Yin
2004-04-28 1:01 ` Nick Yin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY7-F8xQcNuJsG92lJ0000ffaf@hotmail.com \
--to=nickyin@hotmail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).