From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "web@dpdk.org" <web@dpdk.org>
Subject: Request to add to DPDK ecosystem - open-source ethdev test harness
Date: Wed, 30 Nov 2022 10:46:20 +0300 [thread overview]
Message-ID: <5306c001-c7c8-019c-8cad-f052665dc39c@oktetlabs.ru> (raw)
Hi,
I'm sorry for incorrect destination of my previous mail on the topic.
We'd like to add extend DPDK ecosystem with a reference to open-source
test framework [1] which has good coverage for DPDK ethdev.
[1] https://ts-factory.io/
It uses letsencrypt certificate for HTTPs. If it is a problem, please,
let me know and we'll sort it out.
The test harness successfully finds bugs in a number of ethdev
drivers. See the list of reported bugs below:
https://bugs.dpdk.org/show_bug.cgi?id=1097
https://bugs.dpdk.org/show_bug.cgi?id=1102
https://bugs.dpdk.org/show_bug.cgi?id=1108
https://bugs.dpdk.org/show_bug.cgi?id=1109
https://bugs.dpdk.org/show_bug.cgi?id=1110
https://bugs.dpdk.org/show_bug.cgi?id=1111
https://bugs.dpdk.org/show_bug.cgi?id=1113
https://bugs.dpdk.org/show_bug.cgi?id=1115
https://bugs.dpdk.org/show_bug.cgi?id=1122
https://bugs.dpdk.org/show_bug.cgi?id=1125
https://bugs.dpdk.org/show_bug.cgi?id=1126
https://bugs.dpdk.org/show_bug.cgi?id=1127
https://bugs.dpdk.org/show_bug.cgi?id=1129
https://bugs.dpdk.org/show_bug.cgi?id=1132
https://bugs.dpdk.org/show_bug.cgi?id=1134
Expectations for the most of bugs above were added to the database.
So, corresponding failures are not reported as unexpected any more.
Logs for some NICs and DPDK 22.11 are available. Yes, there are many
unexpected results which require classification/analysis. Some looks
like corresponding ethdev driver from my point of view.
Andrew.
reply other threads:[~2022-11-30 7:46 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=5306c001-c7c8-019c-8cad-f052665dc39c@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=web@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).