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] 3e440dd0ecf47f19716503374610ddd75d3a5ce9
Date: Mon, 29 Jul 2024 23:47:28 -0700 (PDT) [thread overview]
Message-ID: <66a88c80.050a0220.66cb3.3168SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
3e440dd0ecf47f19716503374610ddd75d3a5ce9 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#171561
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| mtu_update | PASS |
+-----------------+--------+
| unit_tests_mbuf | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30050/
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-30 14:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 6:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-30 9:25 dpdklab
2024-07-30 9:14 dpdklab
2024-07-30 8:49 dpdklab
2024-07-30 8:44 dpdklab
2024-07-30 8:43 dpdklab
2024-07-30 8:40 dpdklab
2024-07-30 8:34 dpdklab
2024-07-30 8:34 dpdklab
2024-07-30 8:21 dpdklab
2024-07-30 8:16 dpdklab
2024-07-30 8:12 dpdklab
2024-07-30 8:03 dpdklab
2024-07-30 8:02 dpdklab
2024-07-30 7:27 dpdklab
2024-07-30 7:04 dpdklab
2024-07-30 7:03 dpdklab
2024-07-30 7:01 dpdklab
2024-07-30 6:59 dpdklab
2024-07-30 6:50 dpdklab
2024-07-30 6:49 dpdklab
2024-07-30 6:46 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=66a88c80.050a0220.66cb3.3168SMTPIN_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).