From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132602 [PATCH] net/nfp: fix the Tx performance issue
Date: Fri, 13 Oct 2023 06:47:12 -0700 (PDT) [thread overview]
Message-ID: <65294a60.c80a0220.feca4.3a75SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132602
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, October 13 2023 07:46:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:77f913752a55c0262bfda99a1b69ca0bd804c6c7
132602 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27922/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-13 13:47 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 13:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-13 15:17 dpdklab
2023-10-13 14:46 dpdklab
2023-10-13 14:38 dpdklab
2023-10-13 14:12 dpdklab
2023-10-13 14:11 dpdklab
2023-10-13 14:10 dpdklab
2023-10-13 14:09 dpdklab
2023-10-13 14:09 dpdklab
2023-10-13 13:58 dpdklab
2023-10-13 13:54 dpdklab
2023-10-13 13:54 dpdklab
2023-10-13 13:53 dpdklab
2023-10-13 13:52 dpdklab
2023-10-13 13:51 dpdklab
2023-10-13 13:45 dpdklab
2023-10-13 13:31 dpdklab
2023-10-13 13:24 dpdklab
2023-10-13 13:22 dpdklab
2023-10-13 13:17 dpdklab
2023-10-13 13:17 dpdklab
2023-10-13 13:16 dpdklab
2023-10-13 13:16 dpdklab
2023-10-13 13:15 dpdklab
2023-10-13 13:15 dpdklab
2023-10-13 13:14 dpdklab
2023-10-13 13:14 dpdklab
2023-10-13 13:13 dpdklab
2023-10-13 13:13 dpdklab
2023-10-13 13:12 dpdklab
2023-10-13 13:12 dpdklab
2023-10-13 13:12 dpdklab
2023-10-13 13:11 dpdklab
2023-10-13 13:06 dpdklab
2023-10-13 13:04 dpdklab
2023-10-13 13:02 dpdklab
2023-10-13 13:02 dpdklab
2023-10-13 13:02 dpdklab
2023-10-13 13:01 dpdklab
2023-10-13 12:59 dpdklab
2023-10-13 12:58 dpdklab
2023-10-13 12:58 dpdklab
2023-10-13 12:57 dpdklab
2023-10-13 12:48 dpdklab
2023-10-13 12:44 dpdklab
2023-10-13 12:41 dpdklab
2023-10-13 12:40 dpdklab
2023-10-13 12:40 dpdklab
2023-10-13 12:37 dpdklab
2023-10-13 12:30 dpdklab
[not found] <20231013074653.3429-1-chaoyong.he@corigine.com>
2023-10-13 7:27 ` qemudev
2023-10-13 7:31 ` qemudev
2023-10-13 7:47 ` checkpatch
2023-10-13 8:59 ` 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=65294a60.c80a0220.feca4.3a75SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).