From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Bruce Richardson <bruce.richardson@intel.com>
Subject: |SUCCESS| [GIT MASTER] 22d7cbc901607202b4fffd12596cff9d9b7176ea
Date: Sat, 09 Nov 2024 08:33:03 -0800 (PST) [thread overview]
Message-ID: <672f8ebf.050a0220.33440b.4686SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net-intel
22d7cbc901607202b4fffd12596cff9d9b7176ea --> functional testing pass
Upstream job id: Template-DTS-Pipeline#195117
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/31492/
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-09 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 16:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-09 18:39 dpdklab
2024-11-09 17:10 dpdklab
2024-11-09 16:51 dpdklab
2024-11-09 16:45 dpdklab
2024-11-09 16:37 dpdklab
2024-11-09 16:31 dpdklab
2024-11-09 16:29 dpdklab
2024-11-09 16:25 dpdklab
2024-11-09 16:10 dpdklab
2024-11-09 16:09 dpdklab
2024-11-09 16:08 dpdklab
2024-11-09 16:08 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=672f8ebf.050a0220.33440b.4686SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).