From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 2cd2cf0cc53a508c4bd951a980ec534a646260de
Date: Sun, 22 Oct 2023 18:07:38 -0700 (PDT) [thread overview]
Message-ID: <6535c75a.170a0220.2c6a9.f85eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
2cd2cf0cc53a508c4bd951a980ec534a646260de --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26594/
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-23 1:07 UTC|newest]
Thread overview: 197+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 1:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 2:31 dpdklab
2023-10-23 2:07 dpdklab
2023-10-23 2:02 dpdklab
2023-10-23 2:00 dpdklab
2023-10-23 1:59 dpdklab
2023-10-23 1:55 dpdklab
2023-10-23 1:52 dpdklab
2023-10-23 1:51 dpdklab
2023-10-23 1:50 dpdklab
2023-10-23 1:45 dpdklab
2023-10-23 1:37 dpdklab
2023-10-23 1:31 dpdklab
2023-10-23 1:30 dpdklab
2023-10-23 1:29 dpdklab
2023-10-23 1:29 dpdklab
2023-10-23 1:26 dpdklab
2023-10-23 1:25 dpdklab
2023-10-23 1:23 dpdklab
2023-10-23 1:21 dpdklab
2023-10-23 1:20 dpdklab
2023-10-23 1:19 dpdklab
2023-10-23 1:17 dpdklab
2023-10-23 1:17 dpdklab
2023-10-23 1:17 dpdklab
2023-10-23 1:17 dpdklab
2023-10-23 1:16 dpdklab
2023-10-23 1:16 dpdklab
2023-10-23 1:15 dpdklab
2023-10-23 1:15 dpdklab
2023-10-23 1:15 dpdklab
2023-10-23 1:14 dpdklab
2023-10-23 1:13 dpdklab
2023-10-23 1:12 dpdklab
2023-10-23 1:12 dpdklab
2023-10-23 1:12 dpdklab
2023-10-23 1:12 dpdklab
2023-10-23 1:11 dpdklab
2023-10-23 1:11 dpdklab
2023-10-23 1:11 dpdklab
2023-10-23 1:11 dpdklab
2023-10-23 1:10 dpdklab
2023-10-23 1:09 dpdklab
2023-10-23 1:09 dpdklab
2023-10-23 1:09 dpdklab
2023-10-23 1:09 dpdklab
2023-10-23 1:08 dpdklab
2023-10-23 1:08 dpdklab
2023-10-23 1:08 dpdklab
2023-10-23 1:08 dpdklab
2023-10-23 1:07 dpdklab
2023-10-23 1:07 dpdklab
2023-10-23 1:07 dpdklab
2023-10-23 0:57 dpdklab
2023-10-23 0:56 dpdklab
2023-10-22 2:33 dpdklab
2023-10-22 1:42 dpdklab
2023-10-22 1:41 dpdklab
2023-10-22 1:40 dpdklab
2023-10-22 1:38 dpdklab
2023-10-22 1:37 dpdklab
2023-10-22 1:33 dpdklab
2023-10-22 1:33 dpdklab
2023-10-22 1:31 dpdklab
2023-10-22 1:31 dpdklab
2023-10-22 1:30 dpdklab
2023-10-22 1:25 dpdklab
2023-10-22 1:21 dpdklab
2023-10-22 1:21 dpdklab
2023-10-22 1:20 dpdklab
2023-10-22 1:20 dpdklab
2023-10-22 1:20 dpdklab
2023-10-22 1:19 dpdklab
2023-10-22 1:19 dpdklab
2023-10-22 1:19 dpdklab
2023-10-22 1:17 dpdklab
2023-10-22 1:17 dpdklab
2023-10-22 1:15 dpdklab
2023-10-22 1:14 dpdklab
2023-10-22 1:14 dpdklab
2023-10-22 1:13 dpdklab
2023-10-22 1:13 dpdklab
2023-10-22 1:13 dpdklab
2023-10-22 1:13 dpdklab
2023-10-22 1:12 dpdklab
2023-10-22 1:11 dpdklab
2023-10-22 1:11 dpdklab
2023-10-22 1:11 dpdklab
2023-10-22 1:09 dpdklab
2023-10-22 1:09 dpdklab
2023-10-22 1:08 dpdklab
2023-10-22 1:08 dpdklab
2023-10-22 1:08 dpdklab
2023-10-22 1:08 dpdklab
2023-10-22 1:08 dpdklab
2023-10-22 1:07 dpdklab
2023-10-22 1:07 dpdklab
2023-10-22 1:07 dpdklab
2023-10-22 1:07 dpdklab
2023-10-22 1:06 dpdklab
2023-10-22 1:06 dpdklab
2023-10-22 1:05 dpdklab
2023-10-22 1:05 dpdklab
2023-10-22 1:04 dpdklab
2023-10-21 2:20 dpdklab
2023-10-21 2:02 dpdklab
2023-10-21 1:32 dpdklab
2023-10-21 1:31 dpdklab
2023-10-21 1:26 dpdklab
2023-10-21 1:21 dpdklab
2023-10-21 1:20 dpdklab
2023-10-21 1:20 dpdklab
2023-10-21 1:17 dpdklab
2023-10-21 1:17 dpdklab
2023-10-21 1:17 dpdklab
2023-10-21 1:16 dpdklab
2023-10-21 1:16 dpdklab
2023-10-21 1:13 dpdklab
2023-10-21 1:12 dpdklab
2023-10-21 1:11 dpdklab
2023-10-21 1:11 dpdklab
2023-10-21 1:10 dpdklab
2023-10-21 1:08 dpdklab
2023-10-21 1:08 dpdklab
2023-10-21 1:07 dpdklab
2023-10-21 1:07 dpdklab
2023-10-21 1:07 dpdklab
2023-10-21 1:07 dpdklab
2023-10-21 1:06 dpdklab
2023-10-21 1:06 dpdklab
2023-10-21 1:06 dpdklab
2023-10-21 1:06 dpdklab
2023-10-21 1:05 dpdklab
2023-10-21 1:05 dpdklab
2023-10-21 1:05 dpdklab
2023-10-21 1:05 dpdklab
2023-10-21 1:05 dpdklab
2023-10-21 1:05 dpdklab
2023-10-21 1:05 dpdklab
2023-10-21 1:04 dpdklab
2023-10-21 1:04 dpdklab
2023-10-21 1:03 dpdklab
2023-10-21 1:03 dpdklab
2023-10-21 1:03 dpdklab
2023-10-21 1:03 dpdklab
2023-10-21 1:02 dpdklab
2023-10-21 1:02 dpdklab
2023-10-21 1:02 dpdklab
2023-10-21 1:02 dpdklab
2023-10-21 1:01 dpdklab
2023-10-21 1:01 dpdklab
2023-10-21 1:00 dpdklab
2023-10-20 2:21 dpdklab
2023-10-20 1:36 dpdklab
2023-10-20 1:26 dpdklab
2023-10-20 1:25 dpdklab
2023-10-20 1:23 dpdklab
2023-10-20 1:21 dpdklab
2023-10-20 1:21 dpdklab
2023-10-20 1:20 dpdklab
2023-10-20 1:20 dpdklab
2023-10-20 1:20 dpdklab
2023-10-20 1:19 dpdklab
2023-10-20 1:19 dpdklab
2023-10-20 1:18 dpdklab
2023-10-20 1:17 dpdklab
2023-10-20 1:17 dpdklab
2023-10-20 1:17 dpdklab
2023-10-20 1:17 dpdklab
2023-10-20 1:17 dpdklab
2023-10-20 1:16 dpdklab
2023-10-20 1:16 dpdklab
2023-10-20 1:15 dpdklab
2023-10-20 1:15 dpdklab
2023-10-20 1:14 dpdklab
2023-10-20 1:14 dpdklab
2023-10-20 1:14 dpdklab
2023-10-20 1:14 dpdklab
2023-10-20 1:14 dpdklab
2023-10-20 1:14 dpdklab
2023-10-20 1:13 dpdklab
2023-10-20 1:13 dpdklab
2023-10-20 1:13 dpdklab
2023-10-20 1:12 dpdklab
2023-10-20 1:12 dpdklab
2023-10-20 1:12 dpdklab
2023-10-20 1:11 dpdklab
2023-10-20 1:11 dpdklab
2023-10-20 1:10 dpdklab
2023-10-20 1:10 dpdklab
2023-10-20 1:10 dpdklab
2023-10-20 1:10 dpdklab
2023-10-20 1:09 dpdklab
2023-10-20 1:09 dpdklab
2023-10-20 1:09 dpdklab
2023-10-20 1:08 dpdklab
2023-10-20 1:08 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=6535c75a.170a0220.2c6a9.f85eSMTPIN_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).