From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138492-138554 [PATCH] [83/83] bus/dpaa: move alignment a
Date: Wed, 20 Mar 2024 10:28:41 -0700 (PDT) [thread overview]
Message-ID: <65fb1cc9.4a0a0220.40094.8d00SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1710949096-5786-84-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138554
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 20 2024 15:38:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138492-138554 --> 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: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
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: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29603/
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-20 17:28 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710949096-5786-84-git-send-email-roretzla@linux.microsoft.com>
2024-03-20 15:26 ` |SUCCESS| pw138492-138554 [PATCH 83/83] bus/dpaa: move alignment attribute on types qemudev
2024-03-20 15:31 ` qemudev
2024-03-20 15:49 ` |SUCCESS| pw138554 " checkpatch
2024-03-20 16:44 ` |FAILURE| " 0-day Robot
2024-03-20 17:06 ` |SUCCESS| pw138492-138554 [PATCH] [83/83] bus/dpaa: move alignment a dpdklab
2024-03-20 17:21 ` dpdklab
2024-03-20 17:22 ` dpdklab
2024-03-20 17:23 ` dpdklab
2024-03-20 17:23 ` dpdklab
2024-03-20 17:24 ` dpdklab
2024-03-20 17:26 ` dpdklab
2024-03-20 17:26 ` dpdklab
2024-03-20 17:26 ` dpdklab
2024-03-20 17:27 ` dpdklab
2024-03-20 17:27 ` dpdklab
2024-03-20 17:28 ` dpdklab
2024-03-20 17:28 ` dpdklab
2024-03-20 17:28 ` dpdklab [this message]
2024-03-20 17:28 ` dpdklab
2024-03-20 17:29 ` dpdklab
2024-03-20 17:29 ` dpdklab
2024-03-20 17:30 ` dpdklab
2024-03-20 17:30 ` dpdklab
2024-03-20 17:30 ` dpdklab
2024-03-20 17:31 ` dpdklab
2024-03-20 17:31 ` dpdklab
2024-03-20 17:31 ` dpdklab
2024-03-20 17:31 ` dpdklab
2024-03-20 17:31 ` dpdklab
2024-03-20 17:32 ` dpdklab
2024-03-20 17:32 ` dpdklab
2024-03-20 17:32 ` dpdklab
2024-03-20 17:32 ` dpdklab
2024-03-20 17:33 ` dpdklab
2024-03-20 17:33 ` dpdklab
2024-03-20 17:33 ` dpdklab
2024-03-20 17:33 ` dpdklab
2024-03-20 17:33 ` dpdklab
2024-03-20 17:34 ` dpdklab
2024-03-20 17:34 ` dpdklab
2024-03-20 17:34 ` dpdklab
2024-03-20 17:34 ` dpdklab
2024-03-20 17:35 ` dpdklab
2024-03-20 17:35 ` dpdklab
2024-03-20 17:35 ` dpdklab
2024-03-20 17:35 ` dpdklab
2024-03-20 17:36 ` dpdklab
2024-03-20 17:37 ` dpdklab
2024-03-20 17:37 ` dpdklab
2024-03-20 17:37 ` dpdklab
2024-03-20 17:37 ` dpdklab
2024-03-20 17:38 ` dpdklab
2024-03-20 17:39 ` dpdklab
2024-03-20 17:40 ` dpdklab
2024-03-20 17:40 ` dpdklab
2024-03-20 17:44 ` dpdklab
2024-03-20 17:46 ` dpdklab
2024-03-20 17:47 ` dpdklab
2024-03-20 17:47 ` dpdklab
2024-03-20 17:49 ` dpdklab
2024-03-20 18:15 ` dpdklab
2024-03-20 18:19 ` dpdklab
2024-03-20 18:42 ` dpdklab
2024-03-20 18:43 ` dpdklab
2024-03-20 18:43 ` dpdklab
2024-03-20 18:43 ` dpdklab
2024-03-20 18:47 ` dpdklab
2024-03-20 18:48 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 19:16 ` dpdklab
2024-03-20 19:30 ` dpdklab
2024-03-20 19:55 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-22 5:32 ` dpdklab
2024-03-22 6:09 ` 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=65fb1cc9.4a0a0220.40094.8d00SMTPIN_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).