From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 3b017bdc4c25e2cd6733a9363e9c566b95834cc4
Date: Wed, 24 Jul 2024 07:07:01 -0700 (PDT) [thread overview]
Message-ID: <66a10a85.170a0220.251138.6d7bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net-intel
3b017bdc4c25e2cd6733a9363e9c566b95834cc4 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#170401
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/29987/
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-24 14:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 14:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-25 20:13 dpdklab
2024-07-24 20:14 dpdklab
2024-07-24 19:05 dpdklab
2024-07-24 19:04 dpdklab
2024-07-24 18:52 dpdklab
2024-07-24 18:51 dpdklab
2024-07-24 18:35 dpdklab
2024-07-24 18:05 dpdklab
2024-07-24 16:55 dpdklab
2024-07-24 16:04 dpdklab
2024-07-24 15:45 dpdklab
2024-07-24 15:40 dpdklab
2024-07-24 15:10 dpdklab
2024-07-24 15:05 dpdklab
2024-07-24 14:42 dpdklab
2024-07-24 12:41 dpdklab
2024-07-24 12:23 dpdklab
2024-07-24 12:12 dpdklab
2024-07-24 12:11 dpdklab
2024-07-24 12:02 dpdklab
2024-07-24 12:00 dpdklab
2024-07-24 11:57 dpdklab
2024-07-24 11:50 dpdklab
2024-07-24 11:49 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=66a10a85.170a0220.251138.6d7bSMTPIN_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).