From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124352-124354 [PATCH] [v2, 3/3] net/mlx5: enhance the Tx queue affinity
Date: Wed, 22 Feb 2023 16:05:43 +0000 (UTC) [thread overview]
Message-ID: <20230222160543.E343E601B4@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/124354
_Testing PASS_
Submitter: Jiawei Wang <jiaweiw@nvidia.com>
Date: Wednesday, February 22 2023 12:26:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7710b5d15a014872a3aaf646668dafa928ca8473
124352-124354 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| RHEL 7 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25513/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-22 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 16:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-24 5:54 dpdklab
2023-02-22 20:27 dpdklab
2023-02-22 16:15 dpdklab
2023-02-22 16:15 dpdklab
2023-02-22 16:14 dpdklab
2023-02-22 16:11 dpdklab
2023-02-22 16:11 dpdklab
2023-02-22 16:07 dpdklab
2023-02-22 16:04 dpdklab
2023-02-22 16:04 dpdklab
2023-02-22 16:02 dpdklab
2023-02-22 16:00 dpdklab
2023-02-22 15:32 dpdklab
2023-02-22 13:11 dpdklab
2023-02-22 13:07 dpdklab
2023-02-22 13:05 dpdklab
2023-02-22 13:03 dpdklab
2023-02-22 13:00 dpdklab
2023-02-22 12:58 dpdklab
2023-02-22 12:52 dpdklab
2023-02-22 12:51 dpdklab
2023-02-22 12:51 dpdklab
2023-02-22 12:47 dpdklab
[not found] <20230222122628.29627-4-jiaweiw@nvidia.com>
2023-02-22 12:16 ` |SUCCESS| pw124352-124354 [PATCH v2 " qemudev
2023-02-22 12:20 ` qemudev
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=20230222160543.E343E601B4@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--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).