From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] b0fd604534d435cad3ac75fe4fb96b0841084af3
Date: Tue, 09 Jul 2024 02:54:02 -0700 (PDT) [thread overview]
Message-ID: <668d08ba.050a0220.6a0e0.3e45SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
b0fd604534d435cad3ac75fe4fb96b0841084af3 --> 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/29787/
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-09 9:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 9:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-15 4:02 dpdklab
2024-07-15 1:11 dpdklab
2024-07-14 15:38 dpdklab
2024-07-14 9:02 dpdklab
2024-07-13 14:57 dpdklab
2024-07-10 2:29 dpdklab
2024-07-10 2:17 dpdklab
2024-07-10 1:21 dpdklab
2024-07-09 23:13 dpdklab
2024-07-09 23:13 dpdklab
2024-07-09 17:36 dpdklab
2024-07-09 11:41 dpdklab
2024-07-09 11:16 dpdklab
2024-07-09 11:13 dpdklab
2024-07-09 11:08 dpdklab
2024-07-09 10:42 dpdklab
2024-07-09 10:29 dpdklab
2024-07-09 10:12 dpdklab
2024-07-09 9:53 dpdklab
2024-07-09 8:01 dpdklab
2024-07-09 7:36 dpdklab
2024-07-09 7:30 dpdklab
2024-07-09 7:22 dpdklab
2024-07-09 7:18 dpdklab
2024-07-09 7:15 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=668d08ba.050a0220.6a0e0.3e45SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--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).