From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126768 [PATCH] [v2] ethdev: add Tx queue flow matching item
Date: Mon, 08 May 2023 10:01:51 -0700 (PDT) [thread overview]
Message-ID: <64592aff.050a0220.764a5.d4f4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126768
_Testing PASS_
Submitter: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Date: Monday, May 08 2023 13:49:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d03446724972d2a1bb645ce7f3e64f5ef0203d61
126768 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| Debian Bullseye | PASS |
+-----------------+----------+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| RHEL 7 | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26191/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-08 17:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 17:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-08 19:15 dpdklab
2023-05-08 19:14 dpdklab
2023-05-08 18:19 dpdklab
2023-05-08 18:09 dpdklab
2023-05-08 18:01 dpdklab
2023-05-08 17:35 dpdklab
2023-05-08 17:32 dpdklab
2023-05-08 17:14 dpdklab
2023-05-08 17:11 dpdklab
2023-05-08 17:08 dpdklab
2023-05-08 17:07 dpdklab
2023-05-08 17:06 dpdklab
2023-05-08 17:03 dpdklab
2023-05-08 16:58 dpdklab
2023-05-08 16:17 dpdklab
2023-05-08 16:13 dpdklab
2023-05-08 16:12 dpdklab
2023-05-08 16:08 dpdklab
2023-05-08 16:01 dpdklab
2023-05-08 15:59 dpdklab
2023-05-08 15:56 dpdklab
2023-05-08 15:53 dpdklab
2023-05-08 15:53 dpdklab
2023-05-08 15:53 dpdklab
2023-05-08 15:50 dpdklab
2023-05-08 15:49 dpdklab
[not found] <20230508134935.971197-1-kirankumark@marvell.com>
2023-05-08 13:42 ` |SUCCESS| pw126768 [PATCH v2] " qemudev
2023-05-08 13:46 ` qemudev
2023-05-08 14:39 ` 0-day Robot
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=64592aff.050a0220.764a5.d4f4SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).