From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132471-132482 [PATCH] [v6,12/12] baseband/acc: add confi
Date: Wed, 11 Oct 2023 23:45:02 -0700 (PDT) [thread overview]
Message-ID: <652795ee.920a0220.79dca.3c53SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/132482
_Functional Testing PASS_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Tuesday, October 10 2023 20:20:49
DPDK git baseline: Repo:dpdk-next-baseband
Branch: master
CommitID:fbafb3676c482dab60c0b5465b47f2ea33893a36
132471-132482 --> functional testing pass
Test environment and result as below:
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
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27889/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-12 6:45 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 6:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-12 12:48 dpdklab
2023-10-12 6:44 dpdklab
2023-10-12 6:42 dpdklab
2023-10-12 6:33 dpdklab
2023-10-11 13:47 dpdklab
2023-10-11 9:14 dpdklab
2023-10-11 8:21 dpdklab
2023-10-11 8:08 dpdklab
2023-10-11 7:38 dpdklab
2023-10-11 7:37 dpdklab
2023-10-11 7:36 dpdklab
2023-10-11 7:26 dpdklab
2023-10-11 7:24 dpdklab
2023-10-11 7:22 dpdklab
2023-10-11 7:20 dpdklab
2023-10-11 7:19 dpdklab
2023-10-11 7:13 dpdklab
2023-10-11 7:12 dpdklab
2023-10-11 7:11 dpdklab
2023-10-11 7:10 dpdklab
2023-10-11 7:08 dpdklab
2023-10-11 7:06 dpdklab
2023-10-11 7:05 dpdklab
2023-10-11 6:55 dpdklab
2023-10-11 6:53 dpdklab
2023-10-11 6:43 dpdklab
2023-10-11 6:42 dpdklab
2023-10-11 6:40 dpdklab
2023-10-11 6:35 dpdklab
2023-10-11 6:35 dpdklab
2023-10-11 6:34 dpdklab
2023-10-11 6:22 dpdklab
2023-10-11 6:21 dpdklab
2023-10-11 6:20 dpdklab
2023-10-11 6:19 dpdklab
2023-10-11 6:08 dpdklab
2023-10-11 6:03 dpdklab
2023-10-11 6:02 dpdklab
2023-10-11 5:31 dpdklab
2023-10-11 4:57 dpdklab
2023-10-11 4:42 dpdklab
2023-10-11 4:34 dpdklab
2023-10-11 0:42 dpdklab
2023-10-11 0:36 dpdklab
2023-10-10 23:50 dpdklab
2023-10-10 23:45 dpdklab
2023-10-10 23:39 dpdklab
2023-10-10 23:38 dpdklab
2023-10-10 23:35 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=652795ee.920a0220.79dca.3c53SMTPIN_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).