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] 1bbb60642423bb0c3f638f7d63a9e6dd6863785e
Date: Sat, 02 Nov 2024 00:06:42 -0700 (PDT) [thread overview]
Message-ID: <6725cf82.050a0220.3d60aa.a97eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
1bbb60642423bb0c3f638f7d63a9e6dd6863785e --> functional testing pass
Upstream job id: Template-DTS-Pipeline#193744
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| cmdline | PASS |
+-----------------+--------+
| dynamic_queue | PASS |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31405/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-11-02 7:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 7:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-02 9:03 dpdklab
2024-11-02 8:33 dpdklab
2024-11-02 8:32 dpdklab
2024-11-02 8:16 dpdklab
2024-11-02 8:16 dpdklab
2024-11-02 8:15 dpdklab
2024-11-02 7:03 dpdklab
2024-11-02 7:02 dpdklab
2024-11-02 6:58 dpdklab
2024-11-02 6:54 dpdklab
2024-11-02 6:48 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=6725cf82.050a0220.3d60aa.a97eSMTPIN_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).