From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 72B8643F6B; Thu, 2 May 2024 19:16:47 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AE611402B2; Thu, 2 May 2024 19:16:45 +0200 (CEST) Received: from mail-ot1-f43.google.com (mail-ot1-f43.google.com [209.85.210.43]) by mails.dpdk.org (Postfix) with ESMTP id 145BA40299 for ; Thu, 2 May 2024 19:16:44 +0200 (CEST) Received: by mail-ot1-f43.google.com with SMTP id 46e09a7af769-6ee266e2999so2754866a34.2 for ; Thu, 02 May 2024 10:16:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1714670203; x=1715275003; darn=dpdk.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=J/mI8a4YeITJKrfaxd4na5JjKMFH09Jj3QTGXQiR8ic=; b=Fd7Pfx2K3leEUwudF1sk+fxkH7bwc6HsjyB2+MvdyZSaelp4/4qF72SZ/+3TUQW6Dg pK+C6rXFFai7Jgzyj9DrLA6/l/iQ4Vlfias17suSYm6RMWSS34EbclmIglw56jiK4ioS yf55+3/vbgvnjOrxuMuVzfkbn6CqPuU9+E3Vc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714670203; x=1715275003; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=J/mI8a4YeITJKrfaxd4na5JjKMFH09Jj3QTGXQiR8ic=; b=g6YX+pyMAM4Euq9ATqxxHqB6lP+UziNm2eUYPk4Q9wLE5uZyTjoPbBF+CHWExRKvLq 5RDkTa23JoHBTtj8O7yIRkT7B10PqHL4STObwFyn9R45XAUBhDpjcVTClp73/B0erGZ5 DVf6mUUPEeh/aFgLpY6CXJ3glspqXSeLA9e5gpw7F41LBoBprPgxXXmXqeM3dpRTLY15 7jLFvzni3DqesNpxrcoeu6KkQfiBV0L/ek61sH5AdLhQ/9m8jx0QqR6jRbUc0Olc+tLx yYvZFO3HbPpJhg3jyCCTXcgzI4sU1+ACNUdVtOLrLgHxtp42MgE5/M0WliJAD/SPte5b YAfA== X-Gm-Message-State: AOJu0YxKDNMF+jHuSvUFFpIHvJH3XZSTLLOYVb6K20zIiUMKsxhV+mDD FbIT3+v/ybO+cKYhdvlY7mELxQOzoxL5PSuR7vfZVpTHQpREMh+YfoE+BJcuHSQYMUFnZ8nLzt4 fl5jnnJiGGeUgfELeGJ7KVthE/kb0YkRbbt/Rebs/vxLujdC/tzo= X-Google-Smtp-Source: AGHT+IFPcG/5b5+g5m1/y2Q6R/BUmk/pEoQ8qY9ayP0rG1KicrxwdRrVrQrWf4Urh0pzKA6zgd5Wewg0TmMb47iqfKQ= X-Received: by 2002:a05:6830:c6:b0:6ee:39be:e576 with SMTP id x6-20020a05683000c600b006ee39bee576mr564246oto.1.1714670203185; Thu, 02 May 2024 10:16:43 -0700 (PDT) MIME-Version: 1.0 From: Patrick Robb Date: Thu, 2 May 2024 13:16:32 -0400 Message-ID: Subject: DPDK code coverage reports dashboard page To: dev Cc: ci@dpdk.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org 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