From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] eb3ac0962b542552649d565d31997c06f7b63105
Date: Thu, 04 Jul 2024 16:32:48 -0700 (PDT) [thread overview]
Message-ID: <66873120.050a0220.685e1.968eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net-intel
eb3ac0962b542552649d565d31997c06f7b63105 --> 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 |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29725/
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-04 23:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 23:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-08 16:41 dpdklab
2024-07-08 16:27 dpdklab
2024-07-06 14:37 dpdklab
2024-07-06 14:25 dpdklab
2024-07-06 13:01 dpdklab
2024-07-06 3:48 dpdklab
2024-07-05 21:19 dpdklab
2024-07-05 19:10 dpdklab
2024-07-05 14:25 dpdklab
2024-07-05 12:33 dpdklab
2024-07-05 9:30 dpdklab
2024-07-05 9:10 dpdklab
2024-07-05 9:04 dpdklab
2024-07-05 8:59 dpdklab
2024-07-05 8:54 dpdklab
2024-07-05 2:46 dpdklab
2024-07-05 2:14 dpdklab
2024-07-05 0:07 dpdklab
2024-07-04 14:48 dpdklab
2024-07-04 14:17 dpdklab
2024-07-04 14:04 dpdklab
2024-07-04 13:56 dpdklab
2024-07-04 13:43 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=66873120.050a0220.685e1.968eSMTPIN_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).