From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136856 [PATCH] net/nfp: add support of UDP fragmentation
Date: Fri, 16 Feb 2024 18:56:19 -0800 (PST) [thread overview]
Message-ID: <65d02053.810a0220.b334c.9e7fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136856
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Saturday, February 17 2024 01:54:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31d9d436f263a3f4313ad4c029a9905d6be6cbd6
136856 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | 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
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29175/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-17 2:56 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 2:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-17 19:02 dpdklab
2024-02-17 18:54 dpdklab
2024-02-17 4:44 dpdklab
2024-02-17 4:37 dpdklab
2024-02-17 3:53 dpdklab
2024-02-17 3:27 dpdklab
2024-02-17 3:26 dpdklab
2024-02-17 3:25 dpdklab
2024-02-17 3:25 dpdklab
2024-02-17 3:16 dpdklab
2024-02-17 3:14 dpdklab
2024-02-17 3:14 dpdklab
2024-02-17 3:12 dpdklab
2024-02-17 3:09 dpdklab
2024-02-17 3:08 dpdklab
2024-02-17 3:07 dpdklab
2024-02-17 3:04 dpdklab
2024-02-17 3:01 dpdklab
2024-02-17 2:59 dpdklab
2024-02-17 2:58 dpdklab
2024-02-17 2:58 dpdklab
2024-02-17 2:57 dpdklab
2024-02-17 2:57 dpdklab
2024-02-17 2:54 dpdklab
2024-02-17 2:54 dpdklab
2024-02-17 2:54 dpdklab
2024-02-17 2:51 dpdklab
2024-02-17 2:51 dpdklab
2024-02-17 2:50 dpdklab
2024-02-17 2:50 dpdklab
2024-02-17 2:50 dpdklab
2024-02-17 2:49 dpdklab
2024-02-17 2:47 dpdklab
2024-02-17 2:47 dpdklab
2024-02-17 2:46 dpdklab
2024-02-17 2:45 dpdklab
2024-02-17 2:44 dpdklab
2024-02-17 2:44 dpdklab
2024-02-17 2:43 dpdklab
2024-02-17 2:43 dpdklab
2024-02-17 2:43 dpdklab
2024-02-17 2:42 dpdklab
2024-02-17 2:41 dpdklab
2024-02-17 2:40 dpdklab
2024-02-17 2:40 dpdklab
2024-02-17 2:40 dpdklab
2024-02-17 2:38 dpdklab
2024-02-17 2:38 dpdklab
2024-02-17 2:38 dpdklab
2024-02-17 2:36 dpdklab
2024-02-17 2:36 dpdklab
2024-02-17 2:35 dpdklab
2024-02-17 2:35 dpdklab
2024-02-17 2:33 dpdklab
2024-02-17 2:33 dpdklab
2024-02-17 2:33 dpdklab
2024-02-17 2:32 dpdklab
2024-02-17 2:32 dpdklab
2024-02-17 2:32 dpdklab
2024-02-17 2:32 dpdklab
2024-02-17 2:32 dpdklab
2024-02-17 2:31 dpdklab
2024-02-17 2:31 dpdklab
2024-02-17 2:31 dpdklab
2024-02-17 2:31 dpdklab
2024-02-17 2:30 dpdklab
2024-02-17 2:30 dpdklab
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=65d02053.810a0220.b334c.9e7fSMTPIN_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).