From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142730 [PATCH] [v1] dts: add flow rule dataclass to test
Date: Fri, 26 Jul 2024 18:33:51 -0700 (PDT) [thread overview]
Message-ID: <66a44e7f.050a0220.ffec2.fffdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240726142213.3109-1-dmarx@iol.unh.edu>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142730
_Functional Testing PASS_
Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Friday, July 26 2024 14:22:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43
142730 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#171078
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/30630/
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-27 1:34 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240726142213.3109-1-dmarx@iol.unh.edu>
2024-07-26 14:01 ` |SUCCESS| pw142730 [PATCH v1] dts: add flow rule dataclass to testpmd shell qemudev
2024-07-26 14:05 ` qemudev
2024-07-26 14:23 ` checkpatch
2024-07-26 15:23 ` 0-day Robot
2024-07-26 22:07 ` |SUCCESS| pw142730 [PATCH] [v1] dts: add flow rule dataclass to test dpdklab
2024-07-26 22:48 ` dpdklab
2024-07-26 22:52 ` dpdklab
2024-07-26 22:59 ` dpdklab
2024-07-26 23:01 ` dpdklab
2024-07-26 23:02 ` |PENDING| " dpdklab
2024-07-26 23:06 ` |SUCCESS| " dpdklab
2024-07-26 23:08 ` dpdklab
2024-07-27 0:21 ` dpdklab
2024-07-27 0:46 ` |PENDING| " dpdklab
2024-07-27 0:50 ` |SUCCESS| " dpdklab
2024-07-27 0:53 ` |PENDING| " dpdklab
2024-07-27 0:54 ` dpdklab
2024-07-27 0:54 ` dpdklab
2024-07-27 0:55 ` dpdklab
2024-07-27 0:56 ` dpdklab
2024-07-27 0:57 ` dpdklab
2024-07-27 0:57 ` dpdklab
2024-07-27 0:58 ` dpdklab
2024-07-27 1:01 ` dpdklab
2024-07-27 1:04 ` |SUCCESS| " dpdklab
2024-07-27 1:06 ` |PENDING| " dpdklab
2024-07-27 1:06 ` dpdklab
2024-07-27 1:08 ` dpdklab
2024-07-27 1:08 ` dpdklab
2024-07-27 1:10 ` dpdklab
2024-07-27 1:12 ` dpdklab
2024-07-27 1:15 ` dpdklab
2024-07-27 1:18 ` dpdklab
2024-07-27 1:20 ` dpdklab
2024-07-27 1:22 ` dpdklab
2024-07-27 1:26 ` dpdklab
2024-07-27 1:26 ` dpdklab
2024-07-27 1:27 ` dpdklab
2024-07-27 1:29 ` dpdklab
2024-07-27 1:30 ` dpdklab
2024-07-27 1:30 ` dpdklab
2024-07-27 1:30 ` dpdklab
2024-07-27 1:33 ` |SUCCESS| " dpdklab
2024-07-27 1:33 ` |PENDING| " dpdklab
2024-07-27 1:33 ` dpdklab [this message]
2024-07-27 1:36 ` dpdklab
2024-07-27 1:37 ` dpdklab
2024-07-27 1:40 ` dpdklab
2024-07-27 1:41 ` dpdklab
2024-07-27 1:42 ` dpdklab
2024-07-27 1:42 ` dpdklab
2024-07-27 1:52 ` dpdklab
2024-07-27 2:05 ` |SUCCESS| " dpdklab
2024-07-27 3:26 ` 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=66a44e7f.050a0220.ffec2.fffdSMTPIN_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).