From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142558 [PATCH] dts: fix DPDK git tarball cast bug
Date: Sat, 20 Jul 2024 11:40:02 -0700 (PDT) [thread overview]
Message-ID: <669c0482.170a0220.346b88.533cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240719153445.277851-1-alex.chapman@arm.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142558
_Functional Testing PASS_
Submitter: Alex Chapman <alex.chapman@arm.com>
Date: Friday, July 19 2024 15:34:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084
142558 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#169314
Test environment and result as below:
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 |
+------------+--------+
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 |
+------------+--------+
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
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| scatter | PASS |
+-----------------+--------+
| unit_tests_mbuf | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30566/
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-20 18:40 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240719153445.277851-1-alex.chapman@arm.com>
2024-07-19 15:07 ` qemudev
2024-07-19 15:12 ` qemudev
2024-07-19 15:36 ` checkpatch
2024-07-19 16:23 ` 0-day Robot
2024-07-20 18:20 ` dpdklab
2024-07-20 18:22 ` dpdklab
2024-07-20 18:25 ` dpdklab
2024-07-20 18:27 ` dpdklab
2024-07-20 18:29 ` dpdklab
2024-07-20 18:30 ` dpdklab
2024-07-20 18:31 ` dpdklab
2024-07-20 18:32 ` dpdklab
2024-07-20 18:34 ` dpdklab
2024-07-20 18:37 ` |PENDING| " dpdklab
2024-07-20 18:39 ` dpdklab
2024-07-20 18:39 ` dpdklab
2024-07-20 18:39 ` dpdklab
2024-07-20 18:40 ` dpdklab [this message]
2024-07-20 18:40 ` dpdklab
2024-07-20 18:40 ` |SUCCESS| " dpdklab
2024-07-20 18:42 ` |PENDING| " dpdklab
2024-07-20 18:43 ` dpdklab
2024-07-20 18:45 ` |SUCCESS| " dpdklab
2024-07-20 18:46 ` |PENDING| " dpdklab
2024-07-20 18:48 ` dpdklab
2024-07-20 18:48 ` dpdklab
2024-07-20 18:49 ` dpdklab
2024-07-20 18:50 ` dpdklab
2024-07-20 18:51 ` dpdklab
2024-07-20 18:52 ` |SUCCESS| " dpdklab
2024-07-20 18:52 ` dpdklab
2024-07-20 18:54 ` |PENDING| " dpdklab
2024-07-20 18:55 ` dpdklab
2024-07-20 18:56 ` dpdklab
2024-07-20 18:57 ` dpdklab
2024-07-20 18:57 ` dpdklab
2024-07-20 18:57 ` dpdklab
2024-07-20 18:57 ` dpdklab
2024-07-20 18:59 ` dpdklab
2024-07-20 18:59 ` dpdklab
2024-07-20 19:00 ` dpdklab
2024-07-20 19:00 ` dpdklab
2024-07-20 19:02 ` dpdklab
2024-07-20 19:02 ` dpdklab
2024-07-20 19:03 ` dpdklab
2024-07-20 19:04 ` dpdklab
2024-07-20 19:04 ` dpdklab
2024-07-20 19:04 ` |SUCCESS| " dpdklab
2024-07-20 19:04 ` dpdklab
2024-07-20 19:05 ` |PENDING| " dpdklab
2024-07-20 19:06 ` dpdklab
2024-07-20 19:07 ` dpdklab
2024-07-20 19:07 ` dpdklab
2024-07-20 19:08 ` dpdklab
2024-07-20 19:08 ` dpdklab
2024-07-20 19:08 ` dpdklab
2024-07-20 19:08 ` dpdklab
2024-07-20 19:08 ` dpdklab
2024-07-20 19:08 ` dpdklab
2024-07-20 19:08 ` dpdklab
2024-07-20 19:10 ` dpdklab
2024-07-20 19:11 ` dpdklab
2024-07-20 19:12 ` dpdklab
2024-07-20 19:12 ` dpdklab
2024-07-20 19:12 ` dpdklab
2024-07-20 19:14 ` dpdklab
2024-07-20 19:14 ` dpdklab
2024-07-20 19:14 ` dpdklab
2024-07-20 19:14 ` dpdklab
2024-07-20 19:15 ` dpdklab
2024-07-20 19:21 ` dpdklab
2024-07-20 19:21 ` dpdklab
2024-07-20 19:21 ` dpdklab
2024-07-20 19:21 ` dpdklab
2024-07-20 19:21 ` dpdklab
2024-07-20 19:21 ` dpdklab
2024-07-20 19:22 ` dpdklab
2024-07-20 19:22 ` dpdklab
2024-07-20 19:22 ` dpdklab
2024-07-20 19:22 ` dpdklab
2024-07-20 19:23 ` dpdklab
2024-07-20 19:23 ` dpdklab
2024-07-20 19:23 ` dpdklab
2024-07-20 19:23 ` dpdklab
2024-07-20 19:24 ` dpdklab
2024-07-20 19:26 ` |SUCCESS| " dpdklab
2024-07-20 19:27 ` |PENDING| " dpdklab
2024-07-20 19:27 ` dpdklab
2024-07-20 19:28 ` dpdklab
2024-07-20 19:28 ` dpdklab
2024-07-20 19:29 ` dpdklab
2024-07-20 19:30 ` dpdklab
2024-07-20 19:31 ` dpdklab
2024-07-20 19:33 ` dpdklab
2024-07-20 19:34 ` |SUCCESS| " dpdklab
2024-07-20 19:35 ` |PENDING| " dpdklab
2024-07-20 19:35 ` dpdklab
2024-07-20 19:37 ` dpdklab
2024-07-20 19:38 ` dpdklab
2024-07-20 19:39 ` dpdklab
2024-07-20 19:41 ` dpdklab
2024-07-20 19:41 ` dpdklab
2024-07-20 19:42 ` dpdklab
2024-07-20 19:42 ` |SUCCESS| " dpdklab
2024-07-20 19:43 ` |PENDING| " dpdklab
2024-07-20 19:43 ` dpdklab
2024-07-20 19:43 ` dpdklab
2024-07-20 19:44 ` dpdklab
2024-07-20 19:46 ` |SUCCESS| " dpdklab
2024-07-20 19:46 ` dpdklab
2024-07-20 19:54 ` |PENDING| " dpdklab
2024-07-20 20:07 ` dpdklab
2024-07-20 20:23 ` |SUCCESS| " 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=669c0482.170a0220.346b88.533cSMTPIN_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).