From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 972d4c02ae08b1a5b61cdda211896efdc9e9a0d8
Date: Sat, 20 Apr 2024 21:37:58 -0700 (PDT) [thread overview]
Message-ID: <66249826.4a0a0220.c4c4f.1d35SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: tags/v22.11
972d4c02ae08b1a5b61cdda211896efdc9e9a0d8 --> 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 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28900/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-04-21 4:39 UTC|newest]
Thread overview: 183+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 4:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-22 8:29 dpdklab
2024-04-22 8:26 dpdklab
2024-04-22 8:08 dpdklab
2024-04-22 7:26 dpdklab
2024-04-22 6:55 dpdklab
2024-04-22 6:51 dpdklab
2024-04-22 6:35 dpdklab
2024-04-22 6:26 dpdklab
2024-04-22 6:22 dpdklab
2024-04-22 6:07 dpdklab
2024-04-22 5:49 dpdklab
2024-04-22 5:48 dpdklab
2024-04-22 5:44 dpdklab
2024-04-22 5:44 dpdklab
2024-04-22 5:39 dpdklab
2024-04-22 5:38 dpdklab
2024-04-22 5:37 dpdklab
2024-04-22 5:37 dpdklab
2024-04-22 5:37 dpdklab
2024-04-22 5:37 dpdklab
2024-04-22 5:36 dpdklab
2024-04-22 5:36 dpdklab
2024-04-22 5:36 dpdklab
2024-04-22 5:36 dpdklab
2024-04-22 5:35 dpdklab
2024-04-22 5:35 dpdklab
2024-04-22 5:35 dpdklab
2024-04-22 5:35 dpdklab
2024-04-22 5:34 dpdklab
2024-04-22 5:34 dpdklab
2024-04-22 5:33 dpdklab
2024-04-22 5:33 dpdklab
2024-04-22 5:32 dpdklab
2024-04-22 5:32 dpdklab
2024-04-22 5:32 dpdklab
2024-04-22 5:31 dpdklab
2024-04-22 5:31 dpdklab
2024-04-22 5:30 dpdklab
2024-04-22 5:30 dpdklab
2024-04-22 5:30 dpdklab
2024-04-22 5:30 dpdklab
2024-04-22 5:29 dpdklab
2024-04-22 5:29 dpdklab
2024-04-22 5:28 dpdklab
2024-04-22 5:28 dpdklab
2024-04-22 5:28 dpdklab
2024-04-22 5:28 dpdklab
2024-04-22 5:28 dpdklab
2024-04-22 5:27 dpdklab
2024-04-22 5:27 dpdklab
2024-04-22 5:27 dpdklab
2024-04-22 5:27 dpdklab
2024-04-22 5:27 dpdklab
2024-04-22 5:27 dpdklab
2024-04-22 5:26 dpdklab
2024-04-22 5:26 dpdklab
2024-04-22 5:26 dpdklab
2024-04-22 5:25 dpdklab
2024-04-22 5:24 dpdklab
2024-04-22 5:16 dpdklab
2024-04-22 5:12 dpdklab
2024-04-22 5:11 dpdklab
2024-04-22 5:00 dpdklab
2024-04-22 4:48 dpdklab
2024-04-21 7:01 dpdklab
2024-04-21 6:26 dpdklab
2024-04-21 6:20 dpdklab
2024-04-21 6:13 dpdklab
2024-04-21 6:12 dpdklab
2024-04-21 6:12 dpdklab
2024-04-21 6:10 dpdklab
2024-04-21 6:09 dpdklab
2024-04-21 6:07 dpdklab
2024-04-21 6:05 dpdklab
2024-04-21 6:05 dpdklab
2024-04-21 6:03 dpdklab
2024-04-21 6:02 dpdklab
2024-04-21 6:00 dpdklab
2024-04-21 5:58 dpdklab
2024-04-21 5:58 dpdklab
2024-04-21 5:58 dpdklab
2024-04-21 5:57 dpdklab
2024-04-21 5:57 dpdklab
2024-04-21 5:57 dpdklab
2024-04-21 5:56 dpdklab
2024-04-21 5:56 dpdklab
2024-04-21 5:52 dpdklab
2024-04-21 5:48 dpdklab
2024-04-21 5:48 dpdklab
2024-04-21 5:46 dpdklab
2024-04-21 5:42 dpdklab
2024-04-21 5:41 dpdklab
2024-04-21 5:41 dpdklab
2024-04-21 5:40 dpdklab
2024-04-21 5:40 dpdklab
2024-04-21 5:39 dpdklab
2024-04-21 5:39 dpdklab
2024-04-21 5:38 dpdklab
2024-04-21 5:38 dpdklab
2024-04-21 5:37 dpdklab
2024-04-21 5:37 dpdklab
2024-04-21 5:36 dpdklab
2024-04-21 5:36 dpdklab
2024-04-21 5:36 dpdklab
2024-04-21 5:36 dpdklab
2024-04-21 5:35 dpdklab
2024-04-21 5:35 dpdklab
2024-04-21 5:34 dpdklab
2024-04-21 5:33 dpdklab
2024-04-21 5:33 dpdklab
2024-04-21 5:32 dpdklab
2024-04-21 5:31 dpdklab
2024-04-21 5:13 dpdklab
2024-04-21 5:10 dpdklab
2024-04-21 5:06 dpdklab
2024-04-21 5:02 dpdklab
2024-04-21 4:59 dpdklab
2024-04-21 4:45 dpdklab
2024-04-21 4:43 dpdklab
2024-04-21 4:39 dpdklab
2024-04-21 4:36 dpdklab
2024-04-21 4:33 dpdklab
2024-04-21 4:32 dpdklab
2024-04-21 4:32 dpdklab
2024-04-20 7:39 dpdklab
2024-04-20 7:38 dpdklab
2024-04-20 7:22 dpdklab
2024-04-20 7:12 dpdklab
2024-04-20 7:04 dpdklab
2024-04-20 7:04 dpdklab
2024-04-20 7:03 dpdklab
2024-04-20 7:01 dpdklab
2024-04-20 6:57 dpdklab
2024-04-20 6:57 dpdklab
2024-04-20 6:54 dpdklab
2024-04-20 6:54 dpdklab
2024-04-20 6:52 dpdklab
2024-04-20 6:31 dpdklab
2024-04-20 6:27 dpdklab
2024-04-20 6:26 dpdklab
2024-04-20 6:26 dpdklab
2024-04-20 6:24 dpdklab
2024-04-20 6:22 dpdklab
2024-04-20 6:21 dpdklab
2024-04-20 6:20 dpdklab
2024-04-20 6:16 dpdklab
2024-04-20 6:15 dpdklab
2024-04-20 6:15 dpdklab
2024-04-20 6:13 dpdklab
2024-04-20 6:11 dpdklab
2024-04-20 6:09 dpdklab
2024-04-20 6:08 dpdklab
2024-04-20 6:08 dpdklab
2024-04-20 6:08 dpdklab
2024-04-20 6:08 dpdklab
2024-04-20 6:07 dpdklab
2024-04-20 6:06 dpdklab
2024-04-20 6:05 dpdklab
2024-04-20 6:04 dpdklab
2024-04-20 6:03 dpdklab
2024-04-20 6:01 dpdklab
2024-04-20 6:00 dpdklab
2024-04-20 5:59 dpdklab
2024-04-20 5:58 dpdklab
2024-04-20 5:56 dpdklab
2024-04-20 5:55 dpdklab
2024-04-20 5:52 dpdklab
2024-04-20 5:40 dpdklab
2024-04-20 5:39 dpdklab
2024-04-20 5:33 dpdklab
2024-04-20 5:12 dpdklab
2024-04-20 5:11 dpdklab
2024-04-20 5:10 dpdklab
2024-04-20 5:10 dpdklab
2024-04-20 5:10 dpdklab
2024-04-20 5:09 dpdklab
2024-04-20 5:08 dpdklab
2024-04-20 5:08 dpdklab
2024-04-20 5:08 dpdklab
2024-04-20 5:06 dpdklab
2024-04-20 5:05 dpdklab
2024-04-20 5: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=66249826.4a0a0220.c4c4f.1d35SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).