From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 7556a1a355fb377279508735f7afc1faf1d00158
Date: Sat, 17 Jun 2023 18:01:40 -0700 (PDT) [thread overview]
Message-ID: <648e5774.810a0220.2ea50.92cbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
7556a1a355fb377279508735f7afc1faf1d00158 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25066/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-18 1:01 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 1:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-22 14:28 dpdklab
2023-06-22 14:25 dpdklab
2023-06-22 13:38 dpdklab
2023-06-21 5:43 dpdklab
2023-06-21 5:31 dpdklab
2023-06-21 4:12 dpdklab
2023-06-21 4:07 dpdklab
2023-06-21 3:28 dpdklab
2023-06-21 3:23 dpdklab
2023-06-19 20:44 dpdklab
2023-06-19 2:27 dpdklab
2023-06-19 1:22 dpdklab
2023-06-19 1:19 dpdklab
2023-06-19 1:09 dpdklab
2023-06-19 1:04 dpdklab
2023-06-19 1:03 dpdklab
2023-06-19 1:03 dpdklab
2023-06-19 1:02 dpdklab
2023-06-19 1:02 dpdklab
2023-06-19 1:02 dpdklab
2023-06-19 1:02 dpdklab
2023-06-19 1:02 dpdklab
2023-06-19 1:01 dpdklab
2023-06-18 12:18 dpdklab
2023-06-18 5:41 dpdklab
2023-06-18 2:00 dpdklab
2023-06-18 1:57 dpdklab
2023-06-18 1:55 dpdklab
2023-06-18 1:52 dpdklab
2023-06-18 1:32 dpdklab
2023-06-18 1:32 dpdklab
2023-06-18 1:29 dpdklab
2023-06-18 1:26 dpdklab
2023-06-18 1:25 dpdklab
2023-06-18 1:20 dpdklab
2023-06-18 1:19 dpdklab
2023-06-18 1:15 dpdklab
2023-06-18 1:10 dpdklab
2023-06-18 1:04 dpdklab
2023-06-18 1:03 dpdklab
2023-06-18 1:02 dpdklab
2023-06-18 1:02 dpdklab
2023-06-18 1:01 dpdklab
2023-06-18 1:01 dpdklab
2023-06-18 1:01 dpdklab
2023-06-17 8:24 dpdklab
2023-06-17 8:21 dpdklab
2023-06-17 2:04 dpdklab
2023-06-17 2:04 dpdklab
2023-06-17 2:04 dpdklab
2023-06-17 2:03 dpdklab
2023-06-17 1:58 dpdklab
2023-06-17 1:50 dpdklab
2023-06-17 1:42 dpdklab
2023-06-17 1:34 dpdklab
2023-06-17 1:23 dpdklab
2023-06-17 1:23 dpdklab
2023-06-17 1:22 dpdklab
2023-06-17 1:20 dpdklab
2023-06-17 1:20 dpdklab
2023-06-17 1:19 dpdklab
2023-06-17 1:15 dpdklab
2023-06-17 1:09 dpdklab
2023-06-17 1:05 dpdklab
2023-06-17 1:04 dpdklab
2023-06-17 1:03 dpdklab
2023-06-17 1:03 dpdklab
2023-06-17 1:02 dpdklab
2023-06-17 1:00 dpdklab
2023-06-17 0:58 dpdklab
2023-06-16 23:55 dpdklab
2023-06-16 23:46 dpdklab
2023-06-16 23:30 dpdklab
2023-06-16 23:25 dpdklab
2023-06-16 23:20 dpdklab
2023-06-16 4:36 dpdklab
2023-06-16 4:29 dpdklab
2023-06-16 1:49 dpdklab
2023-06-16 1:49 dpdklab
2023-06-16 1:44 dpdklab
2023-06-16 1:40 dpdklab
2023-06-16 1:35 dpdklab
2023-06-16 1:34 dpdklab
2023-06-16 1:34 dpdklab
2023-06-16 1:20 dpdklab
2023-06-16 1:20 dpdklab
2023-06-16 1:12 dpdklab
2023-06-16 1:10 dpdklab
2023-06-16 1:09 dpdklab
2023-06-16 1:04 dpdklab
2023-06-16 1:03 dpdklab
2023-06-16 1:03 dpdklab
2023-06-16 1:02 dpdklab
2023-06-16 1:02 dpdklab
2023-06-16 1:00 dpdklab
2023-06-16 0:59 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=648e5774.810a0220.2ea50.92cbSMTPIN_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).