From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org
Subject: DPDK code coverage reports dashboard page
Date: Thu, 2 May 2024 13:16:32 -0400 [thread overview]
Message-ID: <CAJvnSUDXdJnL3NZ+BYJ3z=RasHDtGSqLDoy_tmsTup+vfK5c5Q@mail.gmail.com> (raw)
Hi DPDK Developers,
I wanted to announce to the mailing lists that the UNH Community Lab
recently rolled out a new page on our dashboard where you can find
code coverage reports for DPDK unit tests.
https://lab.dpdk.org/results/dashboard/code-coverage
It provides some unit test code coverage reports for lib/* and
drivers/*. You can download and extract the test coverage artifacts,
and open up the styled html page by navigating to
out/coveragereport/index.html.
We run these coverage reports 1x/month, on the first day of the month.
Ideally these can serve as a reference for how many lines of code are
touched by unit tests, but also how coverage evolves over time.
Some improvements we have in queue:
-Add driver-tests and perf-tests testsuites. Currently we are only
running fast-tests and a few individual testcases from driver-tests.
-embed the test report (with styling) in the lab dashboard page,
so people don't have to download and open the page locally.
We are building gcov/lcov targets according to the documentation here:
https://mesonbuild.com/Unit-tests.html
Questions or suggestions on how to improve the coverage reports are welcome.
Thanks,
-DPDK Community Lab team
reply other threads:[~2024-05-02 17:16 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='CAJvnSUDXdJnL3NZ+BYJ3z=RasHDtGSqLDoy_tmsTup+vfK5c5Q@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@dpdk.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 read-only IMAP folder(s) and NNTP newsgroup(s).