From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136537-136542 [PATCH] [v7,6/6] baseband/fpga_5gnr_fec: c
Date: Thu, 08 Feb 2024 13:59:02 -0800 (PST) [thread overview]
Message-ID: <65c54ea6.050a0220.2aa4b.1261SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136542
_Functional Testing PASS_
Submitter: Vargas, Hernan <hernan.vargas@intel.com>
Date: Thursday, February 08 2024 16:50:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:263729efd1eb998ba1d7829971ecee620c79d0ce
136537-136542 --> functional testing pass
Test environment and result as below:
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
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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29097/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-08 21:59 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 21:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 23:14 dpdklab
2024-02-08 23:02 dpdklab
2024-02-08 23:01 dpdklab
2024-02-08 22:16 dpdklab
2024-02-08 22:15 dpdklab
2024-02-08 22:12 dpdklab
2024-02-08 22:12 dpdklab
2024-02-08 22:11 dpdklab
2024-02-08 22:10 dpdklab
2024-02-08 22:08 dpdklab
2024-02-08 22:08 dpdklab
2024-02-08 22:07 dpdklab
2024-02-08 22:06 dpdklab
2024-02-08 22:05 dpdklab
2024-02-08 22:05 dpdklab
2024-02-08 22:05 dpdklab
2024-02-08 22:04 dpdklab
2024-02-08 22:04 dpdklab
2024-02-08 22:04 dpdklab
2024-02-08 22:04 dpdklab
2024-02-08 22:03 dpdklab
2024-02-08 22:03 dpdklab
2024-02-08 22:03 dpdklab
2024-02-08 22:02 dpdklab
2024-02-08 21:58 dpdklab
2024-02-08 21:57 dpdklab
2024-02-08 21:57 dpdklab
2024-02-08 21:57 dpdklab
2024-02-08 21:55 dpdklab
2024-02-08 21:55 dpdklab
2024-02-08 21:55 dpdklab
2024-02-08 21:54 dpdklab
2024-02-08 21:53 dpdklab
2024-02-08 21:53 dpdklab
2024-02-08 21:53 dpdklab
2024-02-08 21:53 dpdklab
2024-02-08 21:53 dpdklab
2024-02-08 21:52 dpdklab
2024-02-08 21:52 dpdklab
2024-02-08 21:52 dpdklab
2024-02-08 21:51 dpdklab
2024-02-08 21:50 dpdklab
2024-02-08 21:50 dpdklab
2024-02-08 21:50 dpdklab
2024-02-08 21:50 dpdklab
2024-02-08 21:49 dpdklab
2024-02-08 21:49 dpdklab
2024-02-08 21:48 dpdklab
2024-02-08 21:47 dpdklab
2024-02-08 21:19 dpdklab
2024-02-08 21:19 dpdklab
2024-02-08 21:08 dpdklab
2024-02-08 21:07 dpdklab
2024-02-08 21:07 dpdklab
2024-02-08 21:07 dpdklab
2024-02-08 21:06 dpdklab
2024-02-08 21:04 dpdklab
2024-02-08 21:03 dpdklab
2024-02-08 21:01 dpdklab
2024-02-08 21:00 dpdklab
2024-02-08 21:00 dpdklab
2024-02-08 21:00 dpdklab
2024-02-08 21:00 dpdklab
2024-02-08 20:59 dpdklab
2024-02-08 20:59 dpdklab
2024-02-08 20:58 dpdklab
2024-02-08 20:56 dpdklab
2024-02-08 20:47 dpdklab
2024-02-08 20:31 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=65c54ea6.050a0220.2aa4b.1261SMTPIN_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).