From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135075-135100 [PATCH] [26/26] mempool/dpaa, mempool/dpaa
Date: Tue, 12 Dec 2023 19:10:26 -0800 (PST) [thread overview]
Message-ID: <657920a2.170a0220.27c0d.9987SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135100
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, December 13 2023 01:42:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
135075-135100 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
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
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28603/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-13 3:10 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 3:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-13 6:06 dpdklab
2023-12-13 6:06 dpdklab
2023-12-13 5:58 dpdklab
2023-12-13 5:58 dpdklab
2023-12-13 4:27 dpdklab
2023-12-13 4:08 dpdklab
2023-12-13 4:07 dpdklab
2023-12-13 4:02 dpdklab
2023-12-13 3:49 dpdklab
2023-12-13 3:47 dpdklab
2023-12-13 3:45 dpdklab
2023-12-13 3:43 dpdklab
2023-12-13 3:43 dpdklab
2023-12-13 3:43 dpdklab
2023-12-13 3:35 dpdklab
2023-12-13 3:34 dpdklab
2023-12-13 3:34 dpdklab
2023-12-13 3:33 dpdklab
2023-12-13 3:32 dpdklab
2023-12-13 3:31 dpdklab
2023-12-13 3:30 dpdklab
2023-12-13 3:30 dpdklab
2023-12-13 3:29 dpdklab
2023-12-13 3:26 dpdklab
2023-12-13 3:25 dpdklab
2023-12-13 3:21 dpdklab
2023-12-13 3:19 dpdklab
2023-12-13 3:18 dpdklab
2023-12-13 3:16 dpdklab
2023-12-13 3:13 dpdklab
2023-12-13 3:12 dpdklab
2023-12-13 3:12 dpdklab
2023-12-13 3:08 dpdklab
2023-12-13 3:08 dpdklab
2023-12-13 3:08 dpdklab
2023-12-13 3:07 dpdklab
2023-12-13 3:03 dpdklab
2023-12-13 3:03 dpdklab
2023-12-13 3:02 dpdklab
2023-12-13 3:02 dpdklab
2023-12-13 3:01 dpdklab
2023-12-13 3:01 dpdklab
2023-12-13 2:59 dpdklab
2023-12-13 2:58 dpdklab
2023-12-13 2:58 dpdklab
2023-12-13 2:58 dpdklab
2023-12-13 2:58 dpdklab
2023-12-13 2:57 dpdklab
2023-12-13 2:56 dpdklab
2023-12-13 2:56 dpdklab
2023-12-13 2:56 dpdklab
2023-12-13 2:56 dpdklab
2023-12-13 2:55 dpdklab
2023-12-13 2:55 dpdklab
2023-12-13 2:53 dpdklab
2023-12-13 2:53 dpdklab
2023-12-13 2:48 dpdklab
2023-12-13 2:47 dpdklab
2023-12-13 2:46 dpdklab
2023-12-13 2:43 dpdklab
2023-12-13 2:40 dpdklab
2023-12-13 2:39 dpdklab
2023-12-13 2:39 dpdklab
2023-12-13 2:38 dpdklab
2023-12-13 2:38 dpdklab
2023-12-13 2:38 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=657920a2.170a0220.27c0d.9987SMTPIN_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).