From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143616-143620 [PATCH] [RESEND,v6,8/8] net/hns3: support
Date: Thu, 05 Sep 2024 13:29:20 -0700 (PDT) [thread overview]
Message-ID: <66da14a0.170a0220.ca15b.07ecSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240905062638.7419-9-haijie1@huawei.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143620
_Functional Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Thursday, September 05 2024 06:26:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:523fd7b3adfdf5a87651e8ca33bc69223b3211d5
143616-143620 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#178588
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
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | 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
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30911/
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-09-05 20:29 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240905062638.7419-9-haijie1@huawei.com>
2024-09-05 6:11 ` |SUCCESS| pw143616-143620 [RESEND v6 8/8] net/hns3: support filter registers by module names qemudev
2024-09-05 6:16 ` qemudev
2024-09-05 6:38 ` |SUCCESS| pw143620 " checkpatch
2024-09-05 7:24 ` |FAILURE| " 0-day Robot
2024-09-05 17:40 ` |SUCCESS| pw143616-143620 [PATCH] [RESEND,v6,8/8] net/hns3: support dpdklab
2024-09-05 17:40 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:44 ` dpdklab
2024-09-05 18:06 ` |PENDING| " dpdklab
2024-09-05 18:38 ` |SUCCESS| " dpdklab
2024-09-05 19:04 ` dpdklab
2024-09-05 19:16 ` dpdklab
2024-09-05 19:17 ` dpdklab
2024-09-05 19:18 ` dpdklab
2024-09-05 19:19 ` dpdklab
2024-09-05 19:20 ` dpdklab
2024-09-05 19:31 ` dpdklab
2024-09-05 19:34 ` dpdklab
2024-09-05 19:36 ` dpdklab
2024-09-05 19:37 ` dpdklab
2024-09-05 19:38 ` dpdklab
2024-09-05 19:46 ` dpdklab
2024-09-05 19:54 ` dpdklab
2024-09-05 19:58 ` dpdklab
2024-09-05 19:58 ` dpdklab
2024-09-05 20:09 ` dpdklab
2024-09-05 20:20 ` |PENDING| " dpdklab
2024-09-05 20:29 ` dpdklab [this message]
2024-09-05 20:51 ` |SUCCESS| " dpdklab
2024-09-05 20:52 ` dpdklab
2024-09-05 21:14 ` dpdklab
2024-09-05 21:17 ` dpdklab
2024-09-05 21:24 ` dpdklab
2024-09-05 22:03 ` dpdklab
2024-09-05 22:04 ` dpdklab
2024-09-05 22:05 ` dpdklab
2024-09-05 22:12 ` dpdklab
2024-09-05 22:19 ` dpdklab
2024-09-05 22:20 ` dpdklab
2024-09-05 22:21 ` dpdklab
2024-09-05 22:22 ` dpdklab
2024-09-05 22:24 ` dpdklab
2024-09-05 22:25 ` dpdklab
2024-09-05 22:26 ` dpdklab
2024-09-05 22:26 ` dpdklab
2024-09-05 22:26 ` dpdklab
2024-09-05 22:27 ` dpdklab
2024-09-05 22:28 ` dpdklab
2024-09-05 22:58 ` dpdklab
2024-09-05 23:04 ` dpdklab
2024-09-05 23:05 ` dpdklab
2024-09-05 23:05 ` dpdklab
2024-09-05 23:05 ` dpdklab
2024-09-05 23:05 ` dpdklab
2024-09-05 23:05 ` dpdklab
2024-09-05 23:05 ` dpdklab
2024-09-05 23:06 ` dpdklab
2024-09-05 23:06 ` dpdklab
2024-09-05 23:06 ` dpdklab
2024-09-05 23:07 ` dpdklab
2024-09-05 23:08 ` dpdklab
2024-09-05 23:08 ` dpdklab
2024-09-05 23:55 ` dpdklab
2024-09-05 23:57 ` dpdklab
2024-09-06 0:24 ` dpdklab
2024-09-06 0:25 ` dpdklab
2024-09-06 6:20 ` dpdklab
2024-09-06 6:50 ` dpdklab
2024-09-07 2:41 ` dpdklab
2024-09-07 3:12 ` dpdklab
2024-09-17 22:15 ` dpdklab
2024-09-17 22:33 ` dpdklab
2024-09-17 22:46 ` dpdklab
2024-09-17 23:06 ` 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=66da14a0.170a0220.ca15b.07ecSMTPIN_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).