From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 53483ccd6dee01b8930e7a8c391472453bbe642d
Date: Wed, 20 Mar 2024 00:06:59 -0700 (PDT) [thread overview]
Message-ID: <65fa8b13.020a0220.d3e6e.f6f9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
53483ccd6dee01b8930e7a8c391472453bbe642d --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 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/28551/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-20 7:07 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 7:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-21 21:50 dpdklab
2024-03-21 20:57 dpdklab
2024-03-21 0:26 dpdklab
2024-03-20 8:32 dpdklab
2024-03-20 7:10 dpdklab
2024-03-20 7:04 dpdklab
2024-03-20 7:02 dpdklab
2024-03-20 7:01 dpdklab
2024-03-20 6:59 dpdklab
2024-03-20 6:59 dpdklab
2024-03-20 6:59 dpdklab
2024-03-20 6:59 dpdklab
2024-03-20 6:58 dpdklab
2024-03-20 6:58 dpdklab
2024-03-20 6:57 dpdklab
2024-03-20 6:57 dpdklab
2024-03-20 6:57 dpdklab
2024-03-20 6:57 dpdklab
2024-03-20 6:56 dpdklab
2024-03-20 6:56 dpdklab
2024-03-20 6:56 dpdklab
2024-03-20 6:56 dpdklab
2024-03-20 6:55 dpdklab
2024-03-20 6:55 dpdklab
2024-03-20 6:55 dpdklab
2024-03-20 6:55 dpdklab
2024-03-20 6:55 dpdklab
2024-03-20 6:55 dpdklab
2024-03-20 6:54 dpdklab
2024-03-20 6:54 dpdklab
2024-03-20 6:54 dpdklab
2024-03-20 6:54 dpdklab
2024-03-20 6:53 dpdklab
2024-03-20 6:53 dpdklab
2024-03-20 6:53 dpdklab
2024-03-20 6:53 dpdklab
2024-03-20 6:53 dpdklab
2024-03-20 6:52 dpdklab
2024-03-20 6:52 dpdklab
2024-03-20 6:52 dpdklab
2024-03-20 6:52 dpdklab
2024-03-20 6:52 dpdklab
2024-03-20 6:51 dpdklab
2024-03-20 6:51 dpdklab
2024-03-20 6:51 dpdklab
2024-03-20 6:51 dpdklab
2024-03-20 6:50 dpdklab
2024-03-20 6:50 dpdklab
2024-03-20 6:50 dpdklab
2024-03-20 6:50 dpdklab
2024-03-20 6:50 dpdklab
2024-03-20 6:49 dpdklab
2024-03-20 6:49 dpdklab
2024-03-20 6:49 dpdklab
2024-03-20 6:48 dpdklab
2024-03-20 6:48 dpdklab
2024-03-20 6:48 dpdklab
2024-03-20 6:47 dpdklab
2024-03-20 6:46 dpdklab
2024-03-20 6:45 dpdklab
2024-03-20 6:45 dpdklab
2024-03-20 6:44 dpdklab
2024-03-20 6:44 dpdklab
2024-03-20 6:43 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=65fa8b13.020a0220.d3e6e.f6f9SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--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).