From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 8b362d6d6822814f35eb3cb2a9280db273f96ae6
Date: Tue, 23 Jul 2024 07:03:57 -0700 (PDT) [thread overview]
Message-ID: <669fb84d.4a0a0220.af088.8310SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net-intel
8b362d6d6822814f35eb3cb2a9280db273f96ae6 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#169998
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/29965/
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-23 14:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 14:03 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-24 14:09 dpdklab
2024-07-23 18:57 dpdklab
2024-07-23 18:38 dpdklab
2024-07-23 18:22 dpdklab
2024-07-23 18:21 dpdklab
2024-07-23 18:20 dpdklab
2024-07-23 18:17 dpdklab
2024-07-23 18:15 dpdklab
2024-07-23 18:10 dpdklab
2024-07-23 18:08 dpdklab
2024-07-23 17:36 dpdklab
2024-07-23 17:25 dpdklab
2024-07-23 17:17 dpdklab
2024-07-23 17:10 dpdklab
2024-07-23 16:59 dpdklab
2024-07-23 14:39 dpdklab
2024-07-23 13:19 dpdklab
2024-07-23 13:07 dpdklab
2024-07-23 12:57 dpdklab
2024-07-23 12:55 dpdklab
2024-07-23 12:45 dpdklab
2024-07-23 12:43 dpdklab
2024-07-23 12:42 dpdklab
2024-07-23 12: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=669fb84d.4a0a0220.af088.8310SMTPIN_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).