From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] fa8d2f7f28524a6c8defa3dcd94f5aa131aae084
Date: Fri, 19 Jul 2024 17:32:03 -0700 (PDT) [thread overview]
Message-ID: <669b0583.170a0220.a4b2a.7e36SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
fa8d2f7f28524a6c8defa3dcd94f5aa131aae084 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#169208
Test environment and result as below:
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
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
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29921/
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-20 0:32 UTC|newest]
Thread overview: 184+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 0:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-08 20:44 dpdklab
2024-08-08 20:44 dpdklab
2024-08-08 20:24 dpdklab
2024-08-08 20:23 dpdklab
2024-08-08 20:21 dpdklab
2024-08-08 20:19 dpdklab
2024-08-08 20:14 dpdklab
2024-08-08 19:49 dpdklab
2024-08-08 19:47 dpdklab
2024-08-08 19:46 dpdklab
2024-08-08 19:41 dpdklab
2024-08-08 18:53 dpdklab
2024-08-08 18:46 dpdklab
2024-08-08 18:45 dpdklab
2024-08-08 18:44 dpdklab
2024-08-08 18:38 dpdklab
2024-08-08 18:33 dpdklab
2024-08-08 18:28 dpdklab
2024-08-08 18:28 dpdklab
2024-07-23 17:49 dpdklab
2024-07-23 2:14 dpdklab
2024-07-22 21:14 dpdklab
2024-07-22 21:12 dpdklab
2024-07-22 20:55 dpdklab
2024-07-22 20:55 dpdklab
2024-07-22 20:38 dpdklab
2024-07-22 19:50 dpdklab
2024-07-22 19:30 dpdklab
2024-07-22 19:28 dpdklab
2024-07-22 19:25 dpdklab
2024-07-22 19:13 dpdklab
2024-07-22 18:56 dpdklab
2024-07-22 18:44 dpdklab
2024-07-22 18:36 dpdklab
2024-07-22 18:36 dpdklab
2024-07-22 18:34 dpdklab
2024-07-22 18:28 dpdklab
2024-07-22 18:22 dpdklab
2024-07-22 18:21 dpdklab
2024-07-22 18:20 dpdklab
2024-07-22 2:23 dpdklab
2024-07-22 1:16 dpdklab
2024-07-22 1:16 dpdklab
2024-07-22 1:06 dpdklab
2024-07-22 1:03 dpdklab
2024-07-22 1:02 dpdklab
2024-07-22 0:57 dpdklab
2024-07-22 0:55 dpdklab
2024-07-22 0:53 dpdklab
2024-07-22 0:53 dpdklab
2024-07-22 0:47 dpdklab
2024-07-22 0:44 dpdklab
2024-07-22 0:32 dpdklab
2024-07-22 0:30 dpdklab
2024-07-22 0:25 dpdklab
2024-07-22 0:24 dpdklab
2024-07-22 0:19 dpdklab
2024-07-22 0:16 dpdklab
2024-07-20 2:03 dpdklab
2024-07-20 1:57 dpdklab
2024-07-20 1:20 dpdklab
2024-07-20 1:05 dpdklab
2024-07-20 1:05 dpdklab
2024-07-20 1:04 dpdklab
2024-07-20 1:01 dpdklab
2024-07-20 0:57 dpdklab
2024-07-20 0:54 dpdklab
2024-07-20 0:51 dpdklab
2024-07-20 0:47 dpdklab
2024-07-20 0:43 dpdklab
2024-07-20 0:43 dpdklab
2024-07-20 0:39 dpdklab
2024-07-20 0:34 dpdklab
2024-07-20 0:30 dpdklab
2024-07-20 0:27 dpdklab
2024-07-20 0:26 dpdklab
2024-07-20 0:23 dpdklab
2024-07-20 0:22 dpdklab
2024-07-20 0:21 dpdklab
2024-07-18 14:02 dpdklab
2024-07-18 4:01 dpdklab
2024-07-18 3:40 dpdklab
2024-07-18 3:32 dpdklab
2024-07-18 3:19 dpdklab
2024-07-18 3:17 dpdklab
2024-07-18 2:48 dpdklab
2024-07-18 2:43 dpdklab
2024-07-18 2:15 dpdklab
2024-07-18 2:10 dpdklab
2024-07-18 1:21 dpdklab
2024-07-18 1:13 dpdklab
2024-07-18 0:55 dpdklab
2024-07-18 0:47 dpdklab
2024-07-18 0:44 dpdklab
2024-07-18 0:43 dpdklab
2024-07-18 0:41 dpdklab
2024-07-18 0:41 dpdklab
2024-07-18 0:40 dpdklab
2024-07-18 0:31 dpdklab
2024-07-18 0:29 dpdklab
2024-07-16 23:21 dpdklab
2024-07-16 23:02 dpdklab
2024-07-16 22:58 dpdklab
2024-07-16 22:54 dpdklab
2024-07-16 22:50 dpdklab
2024-07-16 21:44 dpdklab
2024-07-16 19:08 dpdklab
2024-07-16 18:26 dpdklab
2024-07-16 18:21 dpdklab
2024-07-16 18:17 dpdklab
2024-07-16 18:12 dpdklab
2024-07-16 18:02 dpdklab
2024-07-16 15:04 dpdklab
2024-07-16 15:03 dpdklab
2024-07-16 14:44 dpdklab
2024-07-16 14:39 dpdklab
2024-07-16 13:46 dpdklab
2024-07-16 13:45 dpdklab
2024-07-16 12:49 dpdklab
2024-07-16 12:13 dpdklab
2024-07-16 11:54 dpdklab
2024-07-16 11:50 dpdklab
2024-07-16 11:50 dpdklab
2024-07-16 11:46 dpdklab
2024-07-16 11:37 dpdklab
2024-07-16 11:37 dpdklab
2024-07-16 11:36 dpdklab
2024-07-16 11:34 dpdklab
2024-07-16 11:29 dpdklab
2024-07-16 5:34 dpdklab
2024-07-16 5:15 dpdklab
2024-07-16 4:44 dpdklab
2024-07-16 1:10 dpdklab
2024-07-16 1:09 dpdklab
2024-07-16 1:05 dpdklab
2024-07-16 0:49 dpdklab
2024-07-16 0:47 dpdklab
2024-07-16 0:46 dpdklab
2024-07-16 0:46 dpdklab
2024-07-16 0:43 dpdklab
2024-07-16 0:41 dpdklab
2024-07-16 0:36 dpdklab
2024-07-16 0:34 dpdklab
2024-07-16 0:33 dpdklab
2024-07-16 0:33 dpdklab
2024-07-16 0:30 dpdklab
2024-07-16 0:25 dpdklab
2024-07-15 21:55 dpdklab
2024-07-15 21:36 dpdklab
2024-07-15 21:32 dpdklab
2024-07-15 21:27 dpdklab
2024-07-15 21:22 dpdklab
2024-07-14 2:00 dpdklab
2024-07-14 1:19 dpdklab
2024-07-14 1:10 dpdklab
2024-07-14 1:05 dpdklab
2024-07-14 1:05 dpdklab
2024-07-14 0:46 dpdklab
2024-07-14 0:43 dpdklab
2024-07-14 0:42 dpdklab
2024-07-14 0:42 dpdklab
2024-07-14 0:39 dpdklab
2024-07-14 0:31 dpdklab
2024-07-14 0:31 dpdklab
2024-07-14 0:28 dpdklab
2024-07-14 0:27 dpdklab
2024-07-14 0:20 dpdklab
2024-07-13 10:43 dpdklab
2024-07-13 10:02 dpdklab
2024-07-13 9:49 dpdklab
2024-07-13 9:46 dpdklab
2024-07-13 9:18 dpdklab
2024-07-13 8:40 dpdklab
2024-07-13 8:04 dpdklab
2024-07-13 7:26 dpdklab
2024-07-13 7:25 dpdklab
2024-07-13 7:23 dpdklab
2024-07-13 7:20 dpdklab
2024-07-13 7:19 dpdklab
2024-07-13 7:11 dpdklab
2024-07-13 7:11 dpdklab
2024-07-13 7:07 dpdklab
2024-07-13 7:03 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=669b0583.170a0220.a4b2a.7e36SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).