From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1353] Add parallel functional testing support
Date: Wed, 10 Jan 2024 09:59:45 +0000 [thread overview]
Message-ID: <bug-1353-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1353
Bug ID: 1353
Summary: Add parallel functional testing support
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: ---
It’s possible to do parallel functional testing - one NIC in each parallel
execution (two parallel processes/execution can't use the same NIC).
There are multiple ways to do this. Using containers seems the most
straightforward, but maybe we can use Python’s async module.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2833 bytes --]
next reply other threads:[~2024-01-10 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 9:59 bugzilla [this message]
2024-08-07 8:30 ` [DPDK/DTS Bug " bugzilla
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=bug-1353-3@http.bugs.dpdk.org/ \
--to=bugzilla@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 NNTP newsgroup(s).