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] 95bea772528d316c969a170e6206f3b05ac39413
Date: Fri, 05 Jul 2024 07:18:56 -0700 (PDT) [thread overview]
Message-ID: <668800d0.050a0220.738b8.a96bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
95bea772528d316c969a170e6206f3b05ac39413 --> functional testing pass
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
Target: Unknown
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
Target: Unknown
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
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: Unknown
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29733/
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-05 14:18 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 14:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-08 20:56 dpdklab
2024-07-08 20:43 dpdklab
2024-07-06 19:02 dpdklab
2024-07-06 17:37 dpdklab
2024-07-06 17:21 dpdklab
2024-07-06 16:29 dpdklab
2024-07-06 6:19 dpdklab
2024-07-06 4:35 dpdklab
2024-07-06 4:34 dpdklab
2024-07-06 4:34 dpdklab
2024-07-06 4:24 dpdklab
2024-07-05 20:12 dpdklab
2024-07-05 17:10 dpdklab
2024-07-05 16:38 dpdklab
2024-07-05 14:59 dpdklab
2024-07-05 14:59 dpdklab
2024-07-05 14:39 dpdklab
2024-07-05 14:14 dpdklab
2024-07-05 14:09 dpdklab
2024-07-05 14:05 dpdklab
2024-07-05 10:00 dpdklab
2024-07-05 9:42 dpdklab
2024-07-05 9:25 dpdklab
2024-07-05 9:24 dpdklab
2024-07-05 9:18 dpdklab
2024-07-05 9:15 dpdklab
2024-07-05 9:10 dpdklab
2024-07-05 9:08 dpdklab
2024-07-05 4:57 dpdklab
2024-07-05 4:15 dpdklab
2024-07-05 0:28 dpdklab
2024-07-05 0:27 dpdklab
2024-07-04 22:43 dpdklab
2024-07-04 21:46 dpdklab
2024-07-04 21:45 dpdklab
2024-07-04 21:41 dpdklab
2024-07-04 21:40 dpdklab
2024-07-04 16:07 dpdklab
2024-07-04 6:10 dpdklab
2024-07-04 5:57 dpdklab
2024-07-04 5:37 dpdklab
2024-07-04 5:35 dpdklab
2024-07-04 5:32 dpdklab
2024-07-04 5:27 dpdklab
2024-07-04 5:27 dpdklab
2024-07-04 5:21 dpdklab
2024-07-04 2:50 dpdklab
2024-07-04 2:36 dpdklab
2024-07-04 2:31 dpdklab
2024-07-04 2:28 dpdklab
2024-07-04 2:23 dpdklab
2024-07-04 2:16 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=668800d0.050a0220.738b8.a96bSMTPIN_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).