linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	fstests@vger.kernel.org
Cc: oberpar@linux.ibm.com
Subject: bcachefs code coverage analysis
Date: Sat, 17 Jun 2023 20:28:50 -0400	[thread overview]
Message-ID: <ZI5PwpmuGUdWg9Db@moria.home.lan> (raw)

Just got automated gcov analysis going - integrated with the CI. Thanks
Peter for supplying a missing bit of make magic :)

I'll be writing a longer post about ktest/ktestci soon... been doing a
lot of bugfixing and scalability work, it's humming along nicely now.

For now I just wanted to show off the coverage results. ktest now has
gcov variants of our existing tests, we only run these on the most
recent commit of the master branch (vs. the most recent 50 commits for
the other tests), and commits that have gcov results now give you a nice
link to the lcov output, like so:

https://evilpiepirate.org/~testdashboard/ci?branch=bcachefs&commit=26ed392c9add057a503077ad87492d1ab1475407&test=^gcov
https://evilpiepirate.org/~testdashboard/c/26ed392c9add057a503077ad87492d1ab1475407/lcov/fs/bcachefs/index.html

82% line coverage is not too shabby :)

Next up we need to get new-and-improved dynamic fault injection merged:
the code is written, I'm just waiting on memory allocation profiling to
be merged to post it (which has the necessary infrastructure). That will
make it dead easy to add fault injection points for code that isn't
being tested and hook them up to new tests.

                 reply	other threads:[~2023-06-18  0:35 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=ZI5PwpmuGUdWg9Db@moria.home.lan \
    --to=kent.overstreet@linux.dev \
    --cc=fstests@vger.kernel.org \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=oberpar@linux.ibm.com \
    /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).