From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| [GIT MASTER] 94ad302b4ebba4a5b6706a1c43ea0505e5098169
Date: Fri, 20 Dec 2024 02:00:56 -0800 (PST) [thread overview]
Message-ID: <67654058.050a0220.12493d.ab99SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
94ad302b4ebba4a5b6706a1c43ea0505e5098169 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#203586
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/32001/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-20 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 10:00 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-20 11:45 dpdklab
2024-12-20 11:00 dpdklab
2024-12-20 10:47 dpdklab
2024-12-20 10:16 dpdklab
2024-12-20 10:04 dpdklab
2024-12-20 10:00 dpdklab
2024-12-20 9:38 dpdklab
2024-12-20 9:32 dpdklab
2024-12-20 9:26 dpdklab
2024-12-20 9:10 dpdklab
2024-12-20 9:03 dpdklab
2024-12-20 9:03 dpdklab
2024-12-20 8:57 dpdklab
2024-12-20 8:54 dpdklab
2024-12-20 8:45 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=67654058.050a0220.12493d.ab99SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).