From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 5287405d9f8fed3ec20dae1584d76b5cdbf3af0f
Date: Fri, 05 Jul 2024 08:34:49 -0700 (PDT) [thread overview]
Message-ID: <66881299.d40a0220.d09f1.436fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net-intel
5287405d9f8fed3ec20dae1584d76b5cdbf3af0f --> 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/29735/
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-05 15:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 15:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-08 21:59 dpdklab
2024-07-08 21:47 dpdklab
2024-07-06 19:07 dpdklab
2024-07-06 19:05 dpdklab
2024-07-06 17:04 dpdklab
2024-07-06 9:20 dpdklab
2024-07-06 9:19 dpdklab
2024-07-06 5:46 dpdklab
2024-07-06 5:46 dpdklab
2024-07-05 21:38 dpdklab
2024-07-05 17:43 dpdklab
2024-07-05 17:24 dpdklab
2024-07-05 16:53 dpdklab
2024-07-05 16:22 dpdklab
2024-07-05 16:11 dpdklab
2024-07-05 16:05 dpdklab
2024-07-05 16:03 dpdklab
2024-07-05 15:53 dpdklab
2024-07-05 15:30 dpdklab
2024-07-05 15:26 dpdklab
2024-07-05 15:23 dpdklab
2024-07-05 15:16 dpdklab
2024-07-05 15:09 dpdklab
2024-07-05 15:02 dpdklab
2024-07-05 15:01 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=66881299.d40a0220.d09f1.436fSMTPIN_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).