DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: dev <dev@dpdk.org>
Subject: Re: DTS code coverage question
Date: Wed, 08 Jul 2026 17:48:03 +0200	[thread overview]
Message-ID: <py5Ntr2DSbud_I-983p8ug@monjalon.net> (raw)
In-Reply-To: <CAOE1vsNCkhZ8q7ieRAGbJZTFg+xUsjBXXOmegXdoG6L24-Y2HQ@mail.gmail.com>

Hello,

11/06/2026 16:29, Lincoln Lavoie:
> Hello All,
> 
> We have a patch into the 26.07 release that will enable generating
> code coverage reports when DTS is run. The community lab can then
> generate coverage reports, like we do for unit testing
> (https://lab.dpdk.org/results/dashboard/code-coverage).
> 
> The question is, with DTS, tests can run on combinations of NICs, etc.
> So how should those be factored into the reporting.  We can do 1 of
> the following:
> 
> Option 1: Collect coverage reports per NIC / PMD
> Option 2: Aggregate (combine) reports from multiple NICs / PMDs into a
> single report
> Option 3: Only run it on one NIC / PMD, assuming specific PMDs don't
> change the coverage much.
> 
> Is there a specific direction the community would prefer?

As discussed today in the techboard meeting,
we have limited number of NICs in the lab at the moment,
so it's probably better to start small
and focus on the libraries coverage.
If some NICs help to cover more library features, let's combine them.



      reply	other threads:[~2026-07-08 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 14:29 DTS code coverage question Lincoln Lavoie
2026-07-08 15:48 ` Thomas Monjalon [this message]

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=py5Ntr2DSbud_I-983p8ug@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    /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