From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142014 [PATCH] [v6] net/i40e: support FEC feature
Date: Tue, 02 Jul 2024 04:10:52 -0700 (PDT) [thread overview]
Message-ID: <6683e03c.050a0220.497d7.84fdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240702084036.159834-1-zhichaox.zeng@intel.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142014
_Functional Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Tuesday, July 02 2024 08:40:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:47768aac18d7d90d7df29d9d25bbc362c7b4da60
142014 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: Unknown
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| scatter | PASS |
+-----------------+--------+
| unit_tests_mbuf | PASS |
+-----------------+--------+
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: Unknown
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30373/
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:[~2024-07-02 11:10 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240702084036.159834-1-zhichaox.zeng@intel.com>
2024-07-02 8:06 ` |SUCCESS| pw142014 [PATCH v6] " qemudev
2024-07-02 8:10 ` qemudev
2024-07-02 8:31 ` checkpatch
2024-07-02 11:00 ` |SUCCESS| pw142014 [PATCH] [v6] " dpdklab
2024-07-02 11:02 ` dpdklab
2024-07-02 11:04 ` dpdklab
2024-07-02 11:06 ` dpdklab
2024-07-02 11:06 ` dpdklab
2024-07-02 11:10 ` dpdklab [this message]
2024-07-02 11:26 ` dpdklab
2024-07-02 11:31 ` dpdklab
2024-07-02 11:37 ` dpdklab
2024-07-02 12:21 ` |PENDING| " dpdklab
2024-07-02 12:23 ` dpdklab
2024-07-02 12:26 ` dpdklab
2024-07-02 12:27 ` dpdklab
2024-07-02 12:27 ` dpdklab
2024-07-02 12:29 ` |SUCCESS| " dpdklab
2024-07-02 12:32 ` dpdklab
2024-07-02 12:39 ` |PENDING| " dpdklab
2024-07-02 12:48 ` dpdklab
2024-07-02 12:50 ` dpdklab
2024-07-02 12:53 ` dpdklab
2024-07-02 13:02 ` dpdklab
2024-07-02 13:06 ` dpdklab
2024-07-02 13:08 ` dpdklab
2024-07-02 13:08 ` dpdklab
2024-07-02 13:13 ` dpdklab
2024-07-02 13:15 ` dpdklab
2024-07-02 13:19 ` dpdklab
2024-07-02 13:23 ` dpdklab
2024-07-02 13:27 ` dpdklab
2024-07-02 13:27 ` dpdklab
2024-07-02 13:28 ` dpdklab
2024-07-02 13:29 ` dpdklab
2024-07-02 13:36 ` |SUCCESS| " dpdklab
2024-07-02 13:40 ` |PENDING| " dpdklab
2024-07-02 13:45 ` dpdklab
2024-07-02 13:48 ` dpdklab
2024-07-02 13:52 ` dpdklab
2024-07-02 13:52 ` dpdklab
2024-07-02 13:55 ` dpdklab
2024-07-02 13:59 ` dpdklab
2024-07-02 14:03 ` dpdklab
2024-07-02 14:08 ` dpdklab
2024-07-02 14:08 ` dpdklab
2024-07-02 14:11 ` dpdklab
2024-07-02 14:12 ` dpdklab
2024-07-02 14:19 ` dpdklab
2024-07-02 14:23 ` dpdklab
2024-07-02 14:24 ` dpdklab
2024-07-02 14:28 ` dpdklab
2024-07-02 14:30 ` dpdklab
2024-07-02 14:31 ` |SUCCESS| " dpdklab
2024-07-02 15:42 ` |PENDING| " dpdklab
2024-07-02 15:48 ` dpdklab
2024-07-02 15:50 ` dpdklab
2024-07-02 15:52 ` dpdklab
2024-07-02 15:54 ` dpdklab
2024-07-02 15:54 ` dpdklab
2024-07-02 15:54 ` dpdklab
2024-07-02 15:54 ` dpdklab
2024-07-02 15:59 ` dpdklab
2024-07-02 16:00 ` dpdklab
2024-07-02 16:01 ` dpdklab
2024-07-02 16:02 ` dpdklab
2024-07-02 16:02 ` dpdklab
2024-07-02 16:04 ` dpdklab
2024-07-02 16:07 ` dpdklab
2024-07-02 16:09 ` dpdklab
2024-07-02 16:10 ` dpdklab
2024-07-02 16:10 ` dpdklab
2024-07-02 16:13 ` dpdklab
2024-07-02 16:16 ` dpdklab
2024-07-02 16:17 ` dpdklab
2024-07-02 16:17 ` dpdklab
2024-07-02 16:19 ` dpdklab
2024-07-02 16:21 ` dpdklab
2024-07-02 16:32 ` dpdklab
2024-07-02 16:42 ` |SUCCESS| " dpdklab
2024-07-02 16:42 ` dpdklab
2024-07-02 16:46 ` |PENDING| " dpdklab
2024-07-02 16:54 ` dpdklab
2024-07-02 17:01 ` dpdklab
2024-07-02 17:02 ` dpdklab
2024-07-02 17:04 ` |SUCCESS| " dpdklab
2024-07-02 17:06 ` |PENDING| " dpdklab
2024-07-02 17:09 ` dpdklab
2024-07-02 17:32 ` dpdklab
2024-07-02 17:36 ` dpdklab
2024-07-02 17:39 ` dpdklab
2024-07-02 17:39 ` |SUCCESS| " dpdklab
2024-07-02 17:42 ` dpdklab
2024-07-02 17:44 ` |PENDING| " dpdklab
2024-07-02 17:48 ` dpdklab
2024-07-02 17:52 ` dpdklab
2024-07-02 17:56 ` dpdklab
2024-07-02 18:00 ` dpdklab
2024-07-02 18:07 ` dpdklab
2024-07-02 18:24 ` dpdklab
2024-07-02 18:27 ` dpdklab
2024-07-02 18:31 ` dpdklab
2024-07-02 18:34 ` dpdklab
2024-07-02 18:35 ` dpdklab
2024-07-02 18:41 ` dpdklab
2024-07-02 18:42 ` dpdklab
2024-07-02 18:49 ` dpdklab
2024-07-02 19:13 ` |SUCCESS| " dpdklab
2024-07-02 19:44 ` dpdklab
2024-07-02 19:57 ` dpdklab
2024-07-02 21: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=6683e03c.050a0220.497d7.84fdSMTPIN_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).