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 B12F143881; Wed, 10 Jan 2024 10:38:23 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3C72840298; Wed, 10 Jan 2024 10:38:23 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 9D03340269 for ; Wed, 10 Jan 2024 10:38:21 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 7437F43882; Wed, 10 Jan 2024 10:38:21 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1351] Testbed capabilities for test case skipping Date: Wed, 10 Jan 2024 09:38:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: dts X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: juraj.linkes@pantheon.tech X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17048795010.64E73.2457948 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17048795010.64E73.2457948 Date: Wed, 10 Jan 2024 10:38:21 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1351 Bug ID: 1351 Summary: Testbed capabilities for test case skipping Product: DPDK Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: dts Assignee: dev@dpdk.org Reporter: juraj.linkes@pantheon.tech CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu Target Milestone: --- The different hardware DPDK supports is not homogeneous and support a varie= ty of different features. A user-friendly solution would probe the hardware un= der test and skip all test cases that cannot be executed due to missing feature= s. There are multiple dimensions to this task. 1. Device probing. We can leverage existing DPDK probing capabilities in a = DPDK app. A machine-readable output format must be defined, such as json. The fi= elds themselves must be well-defined. 2. Test case/suite marking with required capabilities. If a test case isn't marked, it should run on all hardware. There could be different names for t= he same feature across different hardware, in which case we should decide whet= her we want to merge these under one DTS-defined name or we'll mark each test case/suite with multiple names. --=20 You are receiving this mail because: You are the assignee for the bug.= --17048795010.64E73.2457948 Date: Wed, 10 Jan 2024 10:38:21 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1351
Summary Testbed capabilities for test case skipping
Product DPDK
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity normal
Priority Normal
Component dts
Assignee dev@dpdk.org
Reporter juraj.linkes@pantheon.tech
CC juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone --- 

The different hardware DPDK suppor=
ts is not homogeneous and support a variety
of different features. A user-friendly solution would probe the hardware un=
der
test and skip all test cases that cannot be executed due to missing feature=
s.

There are multiple dimensions to this task.
1. Device probing. We can leverage existing DPDK probing capabilities in a =
DPDK
app. A machine-readable output format must be defined, such as json. The fi=
elds
themselves must be well-defined.
2. Test case/suite marking with required capabilities. If a test case isn't
marked, it should run on all hardware. There could be different names for t=
he
same feature across different hardware, in which case we should decide whet=
her
we want to merge these under one DTS-defined name or we'll mark each test
case/suite with multiple names.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17048795010.64E73.2457948--