From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 367b8db312517edb9f5340d280e77b1437d84dd3
Date: Thu, 30 May 2024 14:56:24 -0700 (PDT) [thread overview]
Message-ID: <6658f608.050a0220.a4d05.240aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-crypto
367b8db312517edb9f5340d280e77b1437d84dd3 --> 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 |
+------------+--------+
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 |
+------------+--------+
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 |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29262/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-05-30 21:56 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 21:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-31 2:24 dpdklab
2024-05-31 1:32 dpdklab
2024-05-31 1:19 dpdklab
2024-05-31 1:18 dpdklab
2024-05-31 1:09 dpdklab
2024-05-31 1:08 dpdklab
2024-05-31 1:06 dpdklab
2024-05-31 1:06 dpdklab
2024-05-31 1:06 dpdklab
2024-05-31 1:05 dpdklab
2024-05-31 1:04 dpdklab
2024-05-31 1:03 dpdklab
2024-05-31 1:03 dpdklab
2024-05-31 0:59 dpdklab
2024-05-31 0:40 dpdklab
2024-05-31 0:40 dpdklab
2024-05-31 0:39 dpdklab
2024-05-31 0:39 dpdklab
2024-05-31 0:38 dpdklab
2024-05-31 0:38 dpdklab
2024-05-31 0:38 dpdklab
2024-05-31 0:38 dpdklab
2024-05-31 0:38 dpdklab
2024-05-31 0:37 dpdklab
2024-05-31 0:37 dpdklab
2024-05-31 0:37 dpdklab
2024-05-31 0:36 dpdklab
2024-05-31 0:36 dpdklab
2024-05-31 0:36 dpdklab
2024-05-31 0:36 dpdklab
2024-05-31 0:35 dpdklab
2024-05-31 0:35 dpdklab
2024-05-31 0:34 dpdklab
2024-05-31 0:18 dpdklab
2024-05-31 0:15 dpdklab
2024-05-31 0:15 dpdklab
2024-05-31 0:15 dpdklab
2024-05-31 0:14 dpdklab
2024-05-31 0:14 dpdklab
2024-05-31 0:14 dpdklab
2024-05-31 0:13 dpdklab
2024-05-31 0:13 dpdklab
2024-05-31 0:13 dpdklab
2024-05-31 0:12 dpdklab
2024-05-31 0:11 dpdklab
2024-05-31 0:10 dpdklab
2024-05-31 0:08 dpdklab
2024-05-31 0:08 dpdklab
2024-05-31 0:06 dpdklab
2024-05-31 0:04 dpdklab
2024-05-31 0:03 dpdklab
2024-05-31 0:00 dpdklab
2024-05-30 23:59 dpdklab
2024-05-30 23:58 dpdklab
2024-05-30 23:54 dpdklab
2024-05-30 23:52 dpdklab
2024-05-30 23:51 dpdklab
2024-05-30 23:50 dpdklab
2024-05-30 23:50 dpdklab
2024-05-30 23:49 dpdklab
2024-05-30 23:49 dpdklab
2024-05-30 23:46 dpdklab
2024-05-30 23:46 dpdklab
2024-05-30 23:45 dpdklab
2024-05-30 23:42 dpdklab
2024-05-30 23:40 dpdklab
2024-05-30 23:02 dpdklab
2024-05-30 22:26 dpdklab
2024-05-30 22:18 dpdklab
2024-05-30 22:18 dpdklab
2024-05-30 22:17 dpdklab
2024-05-30 22:16 dpdklab
2024-05-30 22:15 dpdklab
2024-05-30 22:14 dpdklab
2024-05-30 22:14 dpdklab
2024-05-30 22:06 dpdklab
2024-05-30 22:06 dpdklab
2024-05-30 21:48 dpdklab
2024-05-30 21:48 dpdklab
2024-05-30 21:48 dpdklab
2024-05-30 21:48 dpdklab
2024-05-30 21:47 dpdklab
2024-05-30 21:31 dpdklab
2024-05-30 21:31 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=6658f608.050a0220.a4d05.240aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=gakhil@marvell.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).