From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 5eedf66ac0e5ce62cd333e523996c63a3c4c2c00
Date: Wed, 31 Jan 2024 17:54:28 -0800 (PST) [thread overview]
Message-ID: <65baf9d4.0d0a0220.6a21d.4449SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
5eedf66ac0e5ce62cd333e523996c63a3c4c2c00 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27856/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-01 1:54 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 1:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 3:13 dpdklab
2024-02-01 2:50 dpdklab
2024-02-01 2:33 dpdklab
2024-02-01 2:23 dpdklab
2024-02-01 2:21 dpdklab
2024-02-01 2:19 dpdklab
2024-02-01 2:18 dpdklab
2024-02-01 2:15 dpdklab
2024-02-01 2:14 dpdklab
2024-02-01 2:12 dpdklab
2024-02-01 2:07 dpdklab
2024-02-01 2:07 dpdklab
2024-02-01 2:07 dpdklab
2024-02-01 2:07 dpdklab
2024-02-01 2:07 dpdklab
2024-02-01 2:05 dpdklab
2024-02-01 2:04 dpdklab
2024-02-01 2:04 dpdklab
2024-02-01 2:04 dpdklab
2024-02-01 2:04 dpdklab
2024-02-01 2:04 dpdklab
2024-02-01 2:03 dpdklab
2024-02-01 2:03 dpdklab
2024-02-01 2:01 dpdklab
2024-02-01 2:00 dpdklab
2024-02-01 2:00 dpdklab
2024-02-01 1:59 dpdklab
2024-02-01 1:59 dpdklab
2024-02-01 1:59 dpdklab
2024-02-01 1:59 dpdklab
2024-02-01 1:57 dpdklab
2024-02-01 1:56 dpdklab
2024-02-01 1:53 dpdklab
2024-02-01 1:53 dpdklab
2024-02-01 1:53 dpdklab
2024-02-01 1:53 dpdklab
2024-02-01 1:53 dpdklab
2024-02-01 1:52 dpdklab
2024-02-01 1:52 dpdklab
2024-02-01 1:52 dpdklab
2024-02-01 1:52 dpdklab
2024-02-01 1:52 dpdklab
2024-02-01 1:51 dpdklab
2024-02-01 1:51 dpdklab
2024-02-01 1:51 dpdklab
2024-02-01 1:50 dpdklab
2024-02-01 1:50 dpdklab
2024-02-01 1:50 dpdklab
2024-02-01 1:50 dpdklab
2024-02-01 1:50 dpdklab
2024-02-01 1:49 dpdklab
2024-02-01 1:49 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=65baf9d4.0d0a0220.6a21d.4449SMTPIN_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).