From: Thomas Meyer <thomas@m3y3r.de>
To: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: kselftest on UML results - 4.14.0-rc3-00019-g78d8732cf2d8
Date: Tue, 3 Oct 2017 13:13:00 +0200 [thread overview]
Message-ID: <20171003110145.6we77bub3mmkvyum@olymp> (raw)
Hi,
here are the results from running the kselftests under UML, created with the script
available here:
https://github.com/thomasmey/uml/blob/master/uml-fedora-kselftest.sh
1.) code coverage
http://m3y3r.de/kselftest/4.14.0-rc3-00019-g78d8732cf2d8/coverage/index.html
2.) cyclomatic complexity
http://m3y3r.de/kselftest/4.14.0-rc3-00019-g78d8732cf2d8/result-cyc-comp.txt
3.) kernel build stderr output
http://m3y3r.de/kselftest/4.14.0-rc3-00019-g78d8732cf2d8/result-kernel-build-stderr.txt
4.) kselftests output:
http://m3y3r.de/kselftest/4.14.0-rc3-00019-g78d8732cf2d8/result-kselftests.txt
PS: I have a question regarding the cyclomatic complexity: What is the
meaning of it? I mean I read the definition on Wikipedia, but what do I
do with those results? The ten most "complex" functions are:
Cyclomatic Complexity 730 /home/thomas/git/linux/drivers/md/bcache/super.c:cache_alloc
Cyclomatic Complexity 299 /home/thomas/git/linux/drivers/misc/altera-stapl/altera.c:altera_execute
Cyclomatic Complexity 272 /home/thomas/git/linux/drivers/net/wireless/ti/wl18xx/debugfs.c:wl18xx_debugfs_add_files
Cyclomatic Complexity 266 /home/thomas/git/linux/drivers/md/bcache/super.c:bch_cache_set_alloc
Cyclomatic Complexity 252 /home/thomas/git/linux/fs/ext4/super.c:ext4_fill_super
Cyclomatic Complexity 234 /home/thomas/git/linux/net/core/pktgen.c:pktgen_if_write
Cyclomatic Complexity 220 /home/thomas/git/linux/mm/page_alloc.c:alloc_large_system_hash
Cyclomatic Complexity 218 /home/thomas/git/linux/net/sctp/protocol.c:sctp_init
Cyclomatic Complexity 216 /home/thomas/git/linux/crypto/tcrypt.c:do_test
Cyclomatic Complexity 210 /home/thomas/git/linux/lib/rhashtable.c:rhashtable_init
So is bcache/super.c:cache_alloc a place where bugs lurk?
With kind regards
thomas
reply other threads:[~2017-10-03 11:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171003110145.6we77bub3mmkvyum@olymp \
--to=thomas@m3y3r.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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
all inboxes | Powered by JetHome®