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] a0bb9efc615dd2753788826b1a6ad86024dd298e
Date: Sat, 27 Jul 2024 23:43:59 -0700 (PDT) [thread overview]
Message-ID: <66a5e8af.050a0220.6b0e5.0648SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: tags/v22.11
a0bb9efc615dd2753788826b1a6ad86024dd298e --> functional testing pass
Upstream job id: Template-DTS-Pipeline#171237
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| scatter | PASS |
+-----------------+--------+
| unit_tests_mbuf | PASS |
+-----------------+--------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30032/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-07-28 10:06 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 6:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-29 7:42 dpdklab
2024-07-29 7:15 dpdklab
2024-07-29 6:54 dpdklab
2024-07-29 6:50 dpdklab
2024-07-29 6:48 dpdklab
2024-07-29 6:46 dpdklab
2024-07-29 6:42 dpdklab
2024-07-29 6:36 dpdklab
2024-07-29 6:27 dpdklab
2024-07-29 6:13 dpdklab
2024-07-29 6:13 dpdklab
2024-07-29 5:47 dpdklab
2024-07-29 5:41 dpdklab
2024-07-29 5:37 dpdklab
2024-07-29 5:34 dpdklab
2024-07-29 5:27 dpdklab
2024-07-29 5:23 dpdklab
2024-07-29 5:19 dpdklab
2024-07-29 4:51 dpdklab
2024-07-28 7:41 dpdklab
2024-07-28 7:11 dpdklab
2024-07-28 7:07 dpdklab
2024-07-28 6:55 dpdklab
2024-07-28 6:48 dpdklab
2024-07-28 6:43 dpdklab
2024-07-28 6:16 dpdklab
2024-07-28 6:13 dpdklab
2024-07-28 5:46 dpdklab
2024-07-28 5:38 dpdklab
2024-07-28 5:38 dpdklab
2024-07-28 5:35 dpdklab
2024-07-28 5:33 dpdklab
2024-07-28 5:23 dpdklab
2024-07-28 5:16 dpdklab
2024-07-28 5:11 dpdklab
2024-07-28 4:55 dpdklab
2024-07-28 4:49 dpdklab
2024-07-27 9:37 dpdklab
2024-07-27 7:10 dpdklab
2024-07-27 6:39 dpdklab
2024-07-27 6:32 dpdklab
2024-07-27 6:14 dpdklab
2024-07-27 6:13 dpdklab
2024-07-27 5:47 dpdklab
2024-07-27 5:39 dpdklab
2024-07-27 5:37 dpdklab
2024-07-27 5:33 dpdklab
2024-07-27 5:27 dpdklab
2024-07-27 5:22 dpdklab
2024-07-27 5:16 dpdklab
2024-07-27 4:50 dpdklab
2024-07-26 18:13 dpdklab
2024-07-26 11:19 dpdklab
2024-07-26 9:46 dpdklab
2024-07-26 9:44 dpdklab
2024-07-26 8:56 dpdklab
2024-07-26 8:51 dpdklab
2024-07-26 8:13 dpdklab
2024-07-26 7:29 dpdklab
2024-07-26 7:26 dpdklab
2024-07-26 6:50 dpdklab
2024-07-26 6:42 dpdklab
2024-07-26 6:06 dpdklab
2024-07-26 5:37 dpdklab
2024-07-26 5:34 dpdklab
2024-07-26 5:27 dpdklab
2024-07-26 5:23 dpdklab
2024-07-26 5:21 dpdklab
2024-07-26 5:13 dpdklab
2024-07-26 5:13 dpdklab
2024-07-26 4:55 dpdklab
2024-07-26 4:02 dpdklab
2024-07-25 14:18 dpdklab
2024-07-25 11:57 dpdklab
2024-07-25 8:25 dpdklab
2024-07-25 7:50 dpdklab
2024-07-25 7:48 dpdklab
2024-07-25 7:34 dpdklab
2024-07-25 7:28 dpdklab
2024-07-25 7:23 dpdklab
2024-07-25 7:18 dpdklab
2024-07-25 6:48 dpdklab
2024-07-25 6:29 dpdklab
2024-07-25 6:20 dpdklab
2024-07-25 6:15 dpdklab
2024-07-25 6:07 dpdklab
2024-07-25 6:00 dpdklab
2024-07-25 5:54 dpdklab
2024-07-25 5:20 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=66a5e8af.050a0220.6b0e5.0648SMTPIN_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).