From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chenbo Xia <chenbox@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |SUCCESS| [GIT MASTER] 9cbdb606e5d04de04be3d9f70f0e76551e8c9a36
Date: Sat, 06 Jul 2024 01:24:06 -0700 (PDT) [thread overview]
Message-ID: <6688ff26.050a0220.f1ba1.88a7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-virtio
9cbdb606e5d04de04be3d9f70f0e76551e8c9a36 --> functional testing pass
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
Target: Unknown
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/29750/
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-06 8:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 8:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-15 12:41 dpdklab
2024-07-15 10:51 dpdklab
2024-07-14 18:15 dpdklab
2024-07-14 11:37 dpdklab
2024-07-14 3:13 dpdklab
2024-07-09 5:47 dpdklab
2024-07-09 5:34 dpdklab
2024-07-07 0:51 dpdklab
2024-07-07 0:32 dpdklab
2024-07-06 16:13 dpdklab
2024-07-06 11:10 dpdklab
2024-07-06 11:01 dpdklab
2024-07-06 10:16 dpdklab
2024-07-06 10:09 dpdklab
2024-07-06 9:46 dpdklab
2024-07-06 9:40 dpdklab
2024-07-06 9:35 dpdklab
2024-07-06 9:34 dpdklab
2024-07-06 8:58 dpdklab
2024-07-06 8:39 dpdklab
2024-07-06 8:26 dpdklab
2024-07-06 8:15 dpdklab
2024-07-06 8:13 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=6688ff26.050a0220.f1ba1.88a7SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chenbox@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=maxime.coquelin@redhat.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).