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] 544d6d79a6ff0964a79a57efb102e87fdbd107d9
Date: Wed, 13 Mar 2024 00:03:50 -0700 (PDT) [thread overview]
Message-ID: <65f14fd6.050a0220.f419e.f9cfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
544d6d79a6ff0964a79a57efb102e87fdbd107d9 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
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/28462/
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-13 7:03 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 7:03 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-16 22:17 dpdklab
2024-03-16 21:41 dpdklab
2024-03-13 8:35 dpdklab
2024-03-13 8:20 dpdklab
2024-03-13 7:52 dpdklab
2024-03-13 7:45 dpdklab
2024-03-13 7:37 dpdklab
2024-03-13 7:33 dpdklab
2024-03-13 7:30 dpdklab
2024-03-13 7:30 dpdklab
2024-03-13 7:29 dpdklab
2024-03-13 7:28 dpdklab
2024-03-13 7:28 dpdklab
2024-03-13 7:27 dpdklab
2024-03-13 7:27 dpdklab
2024-03-13 7:26 dpdklab
2024-03-13 7:26 dpdklab
2024-03-13 7:26 dpdklab
2024-03-13 7:26 dpdklab
2024-03-13 7:26 dpdklab
2024-03-13 7:25 dpdklab
2024-03-13 7:25 dpdklab
2024-03-13 7:24 dpdklab
2024-03-13 7:24 dpdklab
2024-03-13 7:24 dpdklab
2024-03-13 7:24 dpdklab
2024-03-13 7:24 dpdklab
2024-03-13 7:23 dpdklab
2024-03-13 7:23 dpdklab
2024-03-13 7:23 dpdklab
2024-03-13 7:23 dpdklab
2024-03-13 7:23 dpdklab
2024-03-13 7:23 dpdklab
2024-03-13 7:22 dpdklab
2024-03-13 7:22 dpdklab
2024-03-13 7:22 dpdklab
2024-03-13 7:22 dpdklab
2024-03-13 7:21 dpdklab
2024-03-13 7:21 dpdklab
2024-03-13 7:21 dpdklab
2024-03-13 7:21 dpdklab
2024-03-13 7:20 dpdklab
2024-03-13 7:20 dpdklab
2024-03-13 7:20 dpdklab
2024-03-13 7:20 dpdklab
2024-03-13 7:19 dpdklab
2024-03-13 7:19 dpdklab
2024-03-13 7:19 dpdklab
2024-03-13 7:19 dpdklab
2024-03-13 7:18 dpdklab
2024-03-13 7:18 dpdklab
2024-03-13 7:18 dpdklab
2024-03-13 7:18 dpdklab
2024-03-13 7:17 dpdklab
2024-03-13 7:16 dpdklab
2024-03-13 7:04 dpdklab
2024-03-13 7:04 dpdklab
2024-03-13 7:03 dpdklab
2024-03-13 7:01 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=65f14fd6.050a0220.f419e.f9cfSMTPIN_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).