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] fe078e1b4a04e1ec55e099c19c4f4915bbf09395
Date: Wed, 28 Feb 2024 22:38:59 -0800 (PST) [thread overview]
Message-ID: <65e02683.810a0220.85b19.2922SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
fe078e1b4a04e1ec55e099c19c4f4915bbf09395 --> 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/28165/
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-29 6:51 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 6:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-29 6:50 dpdklab
2024-02-29 6:46 dpdklab
2024-02-29 6:33 dpdklab
2024-02-28 2:55 dpdklab
2024-02-28 2:41 dpdklab
2024-02-27 23:41 dpdklab
2024-02-27 13:32 dpdklab
2024-02-27 11:56 dpdklab
2024-02-27 11:46 dpdklab
2024-02-27 11:36 dpdklab
2024-02-27 11:31 dpdklab
2024-02-27 11:20 dpdklab
2024-02-27 11:19 dpdklab
2024-02-27 11:19 dpdklab
2024-02-27 11:19 dpdklab
2024-02-27 11:18 dpdklab
2024-02-27 11:18 dpdklab
2024-02-27 11:17 dpdklab
2024-02-27 10:58 dpdklab
2024-02-27 10:56 dpdklab
2024-02-27 10:55 dpdklab
2024-02-27 10:54 dpdklab
2024-02-27 10:52 dpdklab
2024-02-27 10:52 dpdklab
2024-02-27 10:47 dpdklab
2024-02-27 10:46 dpdklab
2024-02-27 10:46 dpdklab
2024-02-27 10:46 dpdklab
2024-02-27 10:46 dpdklab
2024-02-27 10:45 dpdklab
2024-02-27 10:36 dpdklab
2024-02-27 10:28 dpdklab
2024-02-27 10:26 dpdklab
2024-02-27 10:26 dpdklab
2024-02-27 10:26 dpdklab
2024-02-27 10:25 dpdklab
2024-02-27 10:22 dpdklab
2024-02-27 10:22 dpdklab
2024-02-27 10:21 dpdklab
2024-02-27 10:21 dpdklab
2024-02-27 10:21 dpdklab
2024-02-27 10:18 dpdklab
2024-02-27 10:16 dpdklab
2024-02-27 10:16 dpdklab
2024-02-27 10:15 dpdklab
2024-02-27 10:15 dpdklab
2024-02-27 10:04 dpdklab
2024-02-27 10:01 dpdklab
2024-02-27 10:00 dpdklab
2024-02-27 8:21 dpdklab
2024-02-27 8:19 dpdklab
2024-02-27 8:13 dpdklab
2024-02-27 8:09 dpdklab
2024-02-27 8:09 dpdklab
2024-02-27 8:07 dpdklab
2024-02-27 8:02 dpdklab
2024-02-27 8:02 dpdklab
2024-02-27 7:59 dpdklab
2024-02-27 7:57 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=65e02683.810a0220.85b19.2922SMTPIN_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).