From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138013 [PATCH] [v4] net/i40e: support FEC feature
Date: Wed, 06 Mar 2024 08:41:04 -0800 (PST) [thread overview]
Message-ID: <65e89ca0.810a0220.ba847.48caSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240306104135.2805774-1-zhichaox.zeng@intel.com>
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138013
_Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Wednesday, March 06 2024 10:41:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:204425f9c7d8a70202b3fa68a9b44acc2321dd50
138013 --> testing pass
Test environment and result as below:
+----------------------+--------------+
| Environment | lpm_autotest |
+======================+==============+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------+--------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29435/
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-03-06 16:41 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306104135.2805774-1-zhichaox.zeng@intel.com>
2024-03-06 10:11 ` |SUCCESS| pw138013 [PATCH v4] " qemudev
2024-03-06 10:16 ` qemudev
2024-03-06 10:31 ` checkpatch
2024-03-06 11:25 ` 0-day Robot
2024-03-06 14:26 ` |SUCCESS| pw138013 [PATCH] [v4] " dpdklab
2024-03-06 14:27 ` dpdklab
2024-03-06 14:28 ` dpdklab
2024-03-06 14:29 ` dpdklab
2024-03-06 14:30 ` dpdklab
2024-03-06 14:30 ` dpdklab
2024-03-06 14:31 ` dpdklab
2024-03-06 14:32 ` dpdklab
2024-03-06 14:32 ` dpdklab
2024-03-06 14:32 ` dpdklab
2024-03-06 14:50 ` dpdklab
2024-03-06 14:53 ` dpdklab
2024-03-06 15:06 ` dpdklab
2024-03-06 15:07 ` dpdklab
2024-03-06 15:07 ` dpdklab
2024-03-06 15:14 ` dpdklab
2024-03-06 15:22 ` dpdklab
2024-03-06 15:22 ` dpdklab
2024-03-06 15:22 ` dpdklab
2024-03-06 15:23 ` dpdklab
2024-03-06 15:26 ` dpdklab
2024-03-06 15:46 ` dpdklab
2024-03-06 16:15 ` dpdklab
2024-03-06 16:23 ` dpdklab
2024-03-06 16:23 ` dpdklab
2024-03-06 16:24 ` dpdklab
2024-03-06 16:24 ` dpdklab
2024-03-06 16:25 ` dpdklab
2024-03-06 16:25 ` dpdklab
2024-03-06 16:26 ` dpdklab
2024-03-06 16:26 ` dpdklab
2024-03-06 16:27 ` dpdklab
2024-03-06 16:29 ` dpdklab
2024-03-06 16:29 ` dpdklab
2024-03-06 16:29 ` dpdklab
2024-03-06 16:29 ` dpdklab
2024-03-06 16:30 ` dpdklab
2024-03-06 16:30 ` dpdklab
2024-03-06 16:30 ` dpdklab
2024-03-06 16:30 ` dpdklab
2024-03-06 16:32 ` dpdklab
2024-03-06 16:36 ` dpdklab
2024-03-06 16:36 ` dpdklab
2024-03-06 16:41 ` dpdklab [this message]
2024-03-06 16:41 ` dpdklab
2024-03-06 16:48 ` dpdklab
2024-03-06 16:48 ` dpdklab
2024-03-06 16:49 ` dpdklab
2024-03-06 16:49 ` dpdklab
2024-03-06 16:52 ` dpdklab
2024-03-06 16:54 ` dpdklab
2024-03-06 16:54 ` dpdklab
2024-03-06 16:55 ` dpdklab
2024-03-06 16:57 ` dpdklab
2024-03-06 17:06 ` dpdklab
2024-03-06 17:16 ` dpdklab
2024-03-06 17:23 ` dpdklab
2024-03-06 17:24 ` dpdklab
2024-03-06 17:24 ` dpdklab
2024-03-06 17:30 ` dpdklab
2024-03-06 17:55 ` dpdklab
2024-03-06 17:56 ` dpdklab
2024-03-06 17:57 ` dpdklab
2024-03-06 18:01 ` dpdklab
2024-03-06 18:27 ` dpdklab
2024-03-06 18:42 ` dpdklab
2024-03-06 19:07 ` dpdklab
2024-03-06 19:39 ` dpdklab
2024-03-06 22:40 ` 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=65e89ca0.810a0220.ba847.48caSMTPIN_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).