From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] d4af9a82063e4c39568191eaa12955d3ca39581a
Date: Thu, 18 Jan 2024 08:06:06 -0800 (PST) [thread overview]
Message-ID: <65a94c6e.050a0220.a9088.a939SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
d4af9a82063e4c39568191eaa12955d3ca39581a --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27716/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-18 16:06 UTC|newest]
Thread overview: 174+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 16:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 20:37 dpdklab
2024-01-19 0:13 dpdklab
2024-01-18 23:39 dpdklab
2024-01-18 19:11 dpdklab
2024-01-18 18:36 dpdklab
2024-01-18 18:29 dpdklab
2024-01-18 18:29 dpdklab
2024-01-18 18:29 dpdklab
2024-01-18 18:27 dpdklab
2024-01-18 18:24 dpdklab
2024-01-18 18:24 dpdklab
2024-01-18 18:22 dpdklab
2024-01-18 18:21 dpdklab
2024-01-18 18:18 dpdklab
2024-01-18 18:18 dpdklab
2024-01-18 18:16 dpdklab
2024-01-18 18:16 dpdklab
2024-01-18 18:06 dpdklab
2024-01-18 17:53 dpdklab
2024-01-18 17:45 dpdklab
2024-01-18 17:45 dpdklab
2024-01-18 17:44 dpdklab
2024-01-18 17:44 dpdklab
2024-01-18 17:42 dpdklab
2024-01-18 17:34 dpdklab
2024-01-18 17:29 dpdklab
2024-01-18 17:27 dpdklab
2024-01-18 17:27 dpdklab
2024-01-18 17:27 dpdklab
2024-01-18 17:26 dpdklab
2024-01-18 17:26 dpdklab
2024-01-18 17:26 dpdklab
2024-01-18 17:25 dpdklab
2024-01-18 17:24 dpdklab
2024-01-18 17:24 dpdklab
2024-01-18 17:23 dpdklab
2024-01-18 17:22 dpdklab
2024-01-18 17:21 dpdklab
2024-01-18 17:20 dpdklab
2024-01-18 17:20 dpdklab
2024-01-18 17:19 dpdklab
2024-01-18 17:17 dpdklab
2024-01-18 17:16 dpdklab
2024-01-18 17:16 dpdklab
2024-01-18 17:16 dpdklab
2024-01-18 17:15 dpdklab
2024-01-18 17:14 dpdklab
2024-01-18 17:13 dpdklab
2024-01-18 17:13 dpdklab
2024-01-18 17:06 dpdklab
2024-01-18 17:04 dpdklab
2024-01-18 16:44 dpdklab
2024-01-18 16:31 dpdklab
2024-01-18 16:31 dpdklab
2024-01-18 16:17 dpdklab
2024-01-18 16:16 dpdklab
2024-01-18 16:16 dpdklab
2024-01-18 16:07 dpdklab
2024-01-18 16:03 dpdklab
2024-01-17 8:39 dpdklab
2024-01-16 17:50 dpdklab
2024-01-16 4:54 dpdklab
2024-01-16 2:58 dpdklab
2024-01-16 2:48 dpdklab
2024-01-16 2:47 dpdklab
2024-01-16 2:44 dpdklab
2024-01-16 2:41 dpdklab
2024-01-16 2:39 dpdklab
2024-01-16 2:38 dpdklab
2024-01-16 2:36 dpdklab
2024-01-16 2:36 dpdklab
2024-01-16 2:32 dpdklab
2024-01-16 2:31 dpdklab
2024-01-16 2:31 dpdklab
2024-01-16 2:29 dpdklab
2024-01-16 2:26 dpdklab
2024-01-16 2:24 dpdklab
2024-01-16 2:22 dpdklab
2024-01-16 2:22 dpdklab
2024-01-16 2:21 dpdklab
2024-01-16 2:21 dpdklab
2024-01-16 2:20 dpdklab
2024-01-16 2:19 dpdklab
2024-01-16 2:16 dpdklab
2024-01-16 2:16 dpdklab
2024-01-16 2:15 dpdklab
2024-01-16 2:15 dpdklab
2024-01-16 2:14 dpdklab
2024-01-16 2:14 dpdklab
2024-01-16 2:14 dpdklab
2024-01-16 2:14 dpdklab
2024-01-16 2:14 dpdklab
2024-01-16 2:13 dpdklab
2024-01-16 2:13 dpdklab
2024-01-16 2:13 dpdklab
2024-01-16 2:12 dpdklab
2024-01-16 2:12 dpdklab
2024-01-16 2:12 dpdklab
2024-01-16 2:11 dpdklab
2024-01-16 2:11 dpdklab
2024-01-16 2:10 dpdklab
2024-01-16 2:10 dpdklab
2024-01-16 2:10 dpdklab
2024-01-16 2:09 dpdklab
2024-01-16 2:09 dpdklab
2024-01-16 2:08 dpdklab
2024-01-16 2:08 dpdklab
2024-01-16 2:08 dpdklab
2024-01-16 2:07 dpdklab
2024-01-16 2:06 dpdklab
2024-01-16 2:06 dpdklab
2024-01-16 2:05 dpdklab
2024-01-16 2:05 dpdklab
2024-01-16 2:05 dpdklab
2024-01-16 2:04 dpdklab
2024-01-16 2:04 dpdklab
2024-01-16 2:03 dpdklab
2024-01-14 4:50 dpdklab
2024-01-14 2:58 dpdklab
2024-01-14 2:37 dpdklab
2024-01-14 2:33 dpdklab
2024-01-14 2:31 dpdklab
2024-01-14 2:31 dpdklab
2024-01-14 2:31 dpdklab
2024-01-14 2:29 dpdklab
2024-01-14 2:27 dpdklab
2024-01-14 2:26 dpdklab
2024-01-14 2:24 dpdklab
2024-01-14 2:23 dpdklab
2024-01-14 2:21 dpdklab
2024-01-14 2:20 dpdklab
2024-01-14 2:20 dpdklab
2024-01-14 2:19 dpdklab
2024-01-14 2:18 dpdklab
2024-01-14 2:17 dpdklab
2024-01-14 2:17 dpdklab
2024-01-14 2:16 dpdklab
2024-01-14 2:16 dpdklab
2024-01-14 2:13 dpdklab
2024-01-14 2:13 dpdklab
2024-01-14 2:13 dpdklab
2024-01-14 2:13 dpdklab
2024-01-14 2:13 dpdklab
2024-01-14 2:12 dpdklab
2024-01-14 2:11 dpdklab
2024-01-14 2:11 dpdklab
2024-01-14 2:11 dpdklab
2024-01-14 2:11 dpdklab
2024-01-14 2:10 dpdklab
2024-01-14 2:10 dpdklab
2024-01-14 2:10 dpdklab
2024-01-14 2:10 dpdklab
2024-01-14 2:10 dpdklab
2024-01-14 2:09 dpdklab
2024-01-14 2:09 dpdklab
2024-01-14 2:09 dpdklab
2024-01-14 2:09 dpdklab
2024-01-14 2:08 dpdklab
2024-01-14 2:08 dpdklab
2024-01-14 2:08 dpdklab
2024-01-14 2:08 dpdklab
2024-01-14 2:07 dpdklab
2024-01-14 2:07 dpdklab
2024-01-14 2:07 dpdklab
2024-01-14 2:07 dpdklab
2024-01-14 2:06 dpdklab
2024-01-14 2:06 dpdklab
2024-01-14 2:05 dpdklab
2024-01-14 2:05 dpdklab
2024-01-14 2:05 dpdklab
2024-01-14 2:04 dpdklab
2024-01-14 2:04 dpdklab
2024-01-14 2:04 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=65a94c6e.050a0220.a9088.a939SMTPIN_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).