From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152026-152040 [PATCH] [v3,16/16] net/zxdh: provide meter
Date: Tue, 25 Feb 2025 09:45:49 -0800 (PST) [thread overview]
Message-ID: <67be01cd.0d0a0220.5837d.68c7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250225104311.732507-17-wang.junlong1@zte.com.cn>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152040
_Functional Testing PASS_
Submitter: Junlong Wang <wang.junlong1@zte.com.cn>
Date: Tuesday, February 25 2025 10:43:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a9257af8d8f4f2eb93780a48b53e9342f09ebe9a
152026-152040 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#214408
Test environment and result as below:
Ubuntu 24.04 LTS
Kernel: 6.8.0-44-generic
Compiler: gcc 13.2.0
NIC: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ 40 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| mac_filter | PASS |
+------------+--------+
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32680/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-02-25 17:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250225104311.732507-17-wang.junlong1@zte.com.cn>
2025-02-25 10:29 ` |SUCCESS| pw152026-152040 [PATCH v3 16/16] net/zxdh: provide meter ops implementations qemudev
2025-02-25 10:34 ` qemudev
2025-02-25 11:00 ` |SUCCESS| pw152040 " checkpatch
2025-02-25 12:04 ` 0-day Robot
2025-02-25 17:27 ` |SUCCESS| pw152026-152040 [PATCH] [v3,16/16] net/zxdh: provide meter dpdklab
2025-02-25 17:37 ` dpdklab
2025-02-25 17:40 ` dpdklab
2025-02-25 17:45 ` dpdklab [this message]
2025-02-25 17:46 ` dpdklab
2025-02-25 17:55 ` dpdklab
2025-02-25 18:08 ` |PENDING| " dpdklab
2025-02-25 18:36 ` |SUCCESS| " dpdklab
2025-02-25 18:40 ` dpdklab
2025-02-25 18:40 ` dpdklab
2025-02-25 18:44 ` dpdklab
2025-02-25 18:49 ` dpdklab
2025-02-25 18:52 ` dpdklab
2025-02-25 18:53 ` dpdklab
2025-02-25 18:59 ` dpdklab
2025-02-25 19:06 ` |PENDING| " dpdklab
2025-02-25 19:27 ` |SUCCESS| " dpdklab
2025-02-25 19:42 ` dpdklab
2025-02-25 19:47 ` dpdklab
2025-02-25 20:21 ` dpdklab
2025-02-25 20:21 ` |PENDING| " dpdklab
2025-02-25 20:22 ` |SUCCESS| " dpdklab
2025-02-25 20:46 ` |PENDING| " dpdklab
2025-02-25 20:52 ` |SUCCESS| " dpdklab
2025-02-25 21:19 ` dpdklab
2025-02-25 21:21 ` dpdklab
2025-02-25 21:35 ` dpdklab
2025-02-25 22:22 ` |PENDING| " dpdklab
2025-02-25 22:50 ` |SUCCESS| " dpdklab
2025-02-25 23:18 ` 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=67be01cd.0d0a0220.5837d.68c7SMTPIN_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).