From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| [GIT MASTER] 796b031608d8d52e040f83304c676d3cda5af617
Date: Sun, 5 Feb 2023 17:58:45 -0500 (EST) [thread overview]
Message-ID: <20230205225845.5F0C145F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
_Functional Testing PASS_
Branch: dpdk
796b031608d8d52e040f83304c676d3cda5af617 --> 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
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23159/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-05 22:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 22:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-14 4:17 dpdklab
2023-02-10 23:27 dpdklab
2023-02-06 1:13 dpdklab
2023-02-06 1:13 dpdklab
2023-02-06 1:13 dpdklab
2023-02-06 1:12 dpdklab
2023-02-06 1:12 dpdklab
2023-02-06 1:12 dpdklab
2023-02-06 1:04 dpdklab
2023-02-06 0:35 dpdklab
2023-02-06 0:03 dpdklab
2023-02-05 23:22 dpdklab
2023-02-05 23:18 dpdklab
2023-02-05 23:09 dpdklab
2023-02-05 23:09 dpdklab
2023-02-05 23:03 dpdklab
2023-02-05 23:02 dpdklab
2023-02-05 23:02 dpdklab
2023-02-05 23:00 dpdklab
2023-02-05 22:58 dpdklab
2023-02-05 22:54 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=20230205225845.5F0C145F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).