From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 7f82e9c89f3514715533feb34f46ff1ea95c6f98
Date: Sat, 16 Mar 2024 08:57:34 -0700 (PDT) [thread overview]
Message-ID: <65f5c16e.050a0220.41ec9.698fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
7f82e9c89f3514715533feb34f46ff1ea95c6f98 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
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.0-82
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/tarballs/28514/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-16 15:57 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 15:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-20 3:16 dpdklab
2024-03-20 2:40 dpdklab
2024-03-19 21:01 dpdklab
2024-03-19 20:16 dpdklab
2024-03-17 21:29 dpdklab
2024-03-17 20:36 dpdklab
2024-03-17 20:33 dpdklab
2024-03-17 20:28 dpdklab
2024-03-17 20:26 dpdklab
2024-03-17 20:25 dpdklab
2024-03-17 20:24 dpdklab
2024-03-17 20:22 dpdklab
2024-03-17 20:21 dpdklab
2024-03-17 20:20 dpdklab
2024-03-17 20:17 dpdklab
2024-03-17 20:17 dpdklab
2024-03-17 20:17 dpdklab
2024-03-17 20:17 dpdklab
2024-03-17 20:16 dpdklab
2024-03-17 20:16 dpdklab
2024-03-17 20:16 dpdklab
2024-03-17 20:16 dpdklab
2024-03-17 20:15 dpdklab
2024-03-17 20:15 dpdklab
2024-03-17 20:15 dpdklab
2024-03-17 20:15 dpdklab
2024-03-17 20:14 dpdklab
2024-03-17 20:14 dpdklab
2024-03-17 20:14 dpdklab
2024-03-17 20:14 dpdklab
2024-03-17 20:13 dpdklab
2024-03-17 20:13 dpdklab
2024-03-17 20:13 dpdklab
2024-03-17 20:12 dpdklab
2024-03-17 20:12 dpdklab
2024-03-17 20:12 dpdklab
2024-03-17 20:11 dpdklab
2024-03-17 20:11 dpdklab
2024-03-17 20:11 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:07 dpdklab
2024-03-17 20:05 dpdklab
2024-03-16 17:10 dpdklab
2024-03-16 16:31 dpdklab
2024-03-16 16:15 dpdklab
2024-03-16 16:15 dpdklab
2024-03-16 16:10 dpdklab
2024-03-16 16:10 dpdklab
2024-03-16 16:09 dpdklab
2024-03-16 16:08 dpdklab
2024-03-16 16:08 dpdklab
2024-03-16 16:07 dpdklab
2024-03-16 16:07 dpdklab
2024-03-16 16:07 dpdklab
2024-03-16 16:06 dpdklab
2024-03-16 16:06 dpdklab
2024-03-16 16:05 dpdklab
2024-03-16 16:04 dpdklab
2024-03-16 16:04 dpdklab
2024-03-16 16:03 dpdklab
2024-03-16 16:03 dpdklab
2024-03-16 16:02 dpdklab
2024-03-16 16:02 dpdklab
2024-03-16 16:02 dpdklab
2024-03-16 16:01 dpdklab
2024-03-16 16:01 dpdklab
2024-03-16 15:59 dpdklab
2024-03-16 15:59 dpdklab
2024-03-16 15:59 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:57 dpdklab
2024-03-16 15:57 dpdklab
2024-03-16 15:57 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:53 dpdklab
2024-03-16 15:53 dpdklab
2024-03-16 15:53 dpdklab
2024-03-16 15:53 dpdklab
2024-03-16 15:53 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=65f5c16e.050a0220.41ec9.698fSMTPIN_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).