From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 152600d10eebd80e9147b256d61c1dba8731641b
Date: Sat, 04 May 2024 01:55:04 -0700 (PDT) [thread overview]
Message-ID: <6635f7e8.050a0220.dda5a.0adeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: 23.11-staging
152600d10eebd80e9147b256d61c1dba8731641b --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 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
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.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/28986/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-05-04 8:55 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 8:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-04 9:22 dpdklab
2024-05-04 9:18 dpdklab
2024-05-04 9:14 dpdklab
2024-05-04 8:51 dpdklab
2024-05-03 21:19 dpdklab
2024-05-01 5:16 dpdklab
2024-05-01 5:15 dpdklab
2024-05-01 5:07 dpdklab
2024-05-01 4:45 dpdklab
2024-05-01 4:42 dpdklab
2024-05-01 3:55 dpdklab
2024-05-01 3:49 dpdklab
2024-05-01 3:42 dpdklab
2024-05-01 3:38 dpdklab
2024-05-01 3:37 dpdklab
2024-05-01 3:35 dpdklab
2024-05-01 3:34 dpdklab
2024-05-01 3:31 dpdklab
2024-05-01 3:30 dpdklab
2024-05-01 3:27 dpdklab
2024-05-01 3:24 dpdklab
2024-05-01 3:17 dpdklab
2024-05-01 3:03 dpdklab
2024-05-01 3:00 dpdklab
2024-05-01 3:00 dpdklab
2024-05-01 2:58 dpdklab
2024-05-01 2:58 dpdklab
2024-05-01 2:58 dpdklab
2024-05-01 2:56 dpdklab
2024-05-01 2:54 dpdklab
2024-05-01 2:51 dpdklab
2024-05-01 2:49 dpdklab
2024-05-01 2:47 dpdklab
2024-05-01 2:47 dpdklab
2024-05-01 2:47 dpdklab
2024-05-01 2:42 dpdklab
2024-05-01 2:42 dpdklab
2024-05-01 2:41 dpdklab
2024-05-01 2:41 dpdklab
2024-05-01 2:40 dpdklab
2024-05-01 2:40 dpdklab
2024-05-01 2:34 dpdklab
2024-05-01 2:34 dpdklab
2024-05-01 2:33 dpdklab
2024-05-01 2:33 dpdklab
2024-05-01 2:33 dpdklab
2024-05-01 2:32 dpdklab
2024-05-01 2:32 dpdklab
2024-05-01 2:31 dpdklab
2024-05-01 2:30 dpdklab
2024-05-01 2:30 dpdklab
2024-05-01 2:29 dpdklab
2024-05-01 2:28 dpdklab
2024-05-01 2:28 dpdklab
2024-05-01 2:27 dpdklab
2024-05-01 2:26 dpdklab
2024-05-01 2:26 dpdklab
2024-05-01 2:25 dpdklab
2024-05-01 2:24 dpdklab
2024-05-01 2:24 dpdklab
2024-05-01 2:20 dpdklab
2024-05-01 2:18 dpdklab
2024-05-01 2:18 dpdklab
2024-05-01 2:18 dpdklab
2024-05-01 2:18 dpdklab
2024-05-01 2:18 dpdklab
2024-05-01 2:18 dpdklab
2024-05-01 2:17 dpdklab
2024-05-01 2:17 dpdklab
2024-05-01 2:17 dpdklab
2024-05-01 2:16 dpdklab
2024-05-01 2:16 dpdklab
2024-05-01 2:16 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=6635f7e8.050a0220.dda5a.0adeSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).