From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 82c47f005b9a0a1e3a649664b7713443d18abe43
Date: Sat, 27 Jul 2024 17:18:46 -0700 (PDT) [thread overview]
Message-ID: <66a58e66.170a0220.24d6ac.c540SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
82c47f005b9a0a1e3a649664b7713443d18abe43 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#171182
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 |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30029/
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 0:18 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 0:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-28 1:55 dpdklab
2024-07-28 1:55 dpdklab
2024-07-28 1:27 dpdklab
2024-07-28 1:17 dpdklab
2024-07-28 1:13 dpdklab
2024-07-28 1:04 dpdklab
2024-07-28 1:03 dpdklab
2024-07-28 1:02 dpdklab
2024-07-28 0:50 dpdklab
2024-07-28 0:48 dpdklab
2024-07-28 0:44 dpdklab
2024-07-28 0:44 dpdklab
2024-07-28 0:41 dpdklab
2024-07-28 0:30 dpdklab
2024-07-28 0:29 dpdklab
2024-07-28 0:28 dpdklab
2024-07-28 0:26 dpdklab
2024-07-28 0:24 dpdklab
2024-07-28 0:24 dpdklab
2024-07-26 18:29 dpdklab
2024-07-26 18:25 dpdklab
2024-07-26 14:56 dpdklab
2024-07-26 8:52 dpdklab
2024-07-26 1:31 dpdklab
2024-07-26 1:15 dpdklab
2024-07-26 1:05 dpdklab
2024-07-26 1:04 dpdklab
2024-07-26 1:04 dpdklab
2024-07-26 1:04 dpdklab
2024-07-26 1:04 dpdklab
2024-07-26 1:03 dpdklab
2024-07-26 0:30 dpdklab
2024-07-26 0:28 dpdklab
2024-07-26 0:26 dpdklab
2024-07-26 0:25 dpdklab
2024-07-26 0:20 dpdklab
2024-07-26 0:19 dpdklab
2024-07-25 23:39 dpdklab
2024-07-25 17:01 dpdklab
2024-07-25 16:43 dpdklab
2024-07-25 15:15 dpdklab
2024-07-25 13:08 dpdklab
2024-07-25 12:40 dpdklab
2024-07-25 10:15 dpdklab
2024-07-25 10:12 dpdklab
2024-07-25 9:40 dpdklab
2024-07-25 9:40 dpdklab
2024-07-25 9:20 dpdklab
2024-07-25 9:14 dpdklab
2024-07-25 9:09 dpdklab
2024-07-25 8:35 dpdklab
2024-07-25 8:30 dpdklab
2024-07-25 8:28 dpdklab
2024-07-25 8:27 dpdklab
2024-07-25 8:16 dpdklab
2024-07-25 8:15 dpdklab
2024-07-25 8:13 dpdklab
2024-07-25 8:08 dpdklab
2024-07-25 8:07 dpdklab
2024-07-25 6:24 dpdklab
2024-07-25 6:05 dpdklab
2024-07-25 5:58 dpdklab
2024-07-25 4:31 dpdklab
2024-07-25 0:13 dpdklab
2024-07-25 0:06 dpdklab
2024-07-25 0:00 dpdklab
2024-07-24 23:25 dpdklab
2024-07-24 23:22 dpdklab
2024-07-24 23:17 dpdklab
2024-07-24 23:17 dpdklab
2024-07-24 23:12 dpdklab
2024-07-24 23:08 dpdklab
2024-07-24 22:24 dpdklab
2024-07-24 22:08 dpdklab
2024-07-24 22:08 dpdklab
2024-07-24 22:01 dpdklab
2024-07-24 21:55 dpdklab
2024-07-24 21:54 dpdklab
2024-07-24 21:49 dpdklab
2024-07-24 21:47 dpdklab
2024-07-24 5:14 dpdklab
2024-07-24 4:15 dpdklab
2024-07-24 3:57 dpdklab
2024-07-24 3:48 dpdklab
2024-07-24 3:17 dpdklab
2024-07-24 2:57 dpdklab
2024-07-24 2:52 dpdklab
2024-07-24 2:52 dpdklab
2024-07-24 2:47 dpdklab
2024-07-24 2:42 dpdklab
2024-07-24 2:17 dpdklab
2024-07-24 2:08 dpdklab
2024-07-24 1:55 dpdklab
2024-07-24 1:52 dpdklab
2024-07-24 1:51 dpdklab
2024-07-24 1:46 dpdklab
2024-07-24 1:42 dpdklab
2024-07-24 1:39 dpdklab
2024-07-24 1:35 dpdklab
2024-07-24 1:35 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=66a58e66.170a0220.24d6ac.c540SMTPIN_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).