From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 012b02bdbc95a5ec3b293f2d37d8955140fd8831
Date: Thu, 14 Nov 2024 17:15:38 -0800 (PST) [thread overview]
Message-ID: <6736a0ba.a70a0220.2418b5.181fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-eventdev
012b02bdbc95a5ec3b293f2d37d8955140fd8831 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#196653
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/31588/
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-15 1:15 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 1:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-15 0:47 dpdklab
2024-11-15 0:43 dpdklab
2024-11-15 0:41 dpdklab
2024-11-15 0:21 dpdklab
2024-11-14 1:26 dpdklab
2024-11-14 1:19 dpdklab
2024-11-14 1:05 dpdklab
2024-11-14 0:40 dpdklab
2024-11-14 0:15 dpdklab
2024-11-14 0:09 dpdklab
2024-11-13 23:40 dpdklab
2024-11-13 21:54 dpdklab
2024-11-13 20:34 dpdklab
2024-11-13 20:25 dpdklab
2024-11-13 19:42 dpdklab
2024-11-13 19:34 dpdklab
2024-11-09 0:22 dpdklab
2024-11-08 23:27 dpdklab
2024-11-08 23:19 dpdklab
2024-11-08 23:11 dpdklab
2024-11-08 21:09 dpdklab
2024-11-08 20:55 dpdklab
2024-11-08 20:41 dpdklab
2024-11-08 20:32 dpdklab
2024-11-08 20:24 dpdklab
2024-11-08 20:07 dpdklab
2024-11-08 19:59 dpdklab
2024-11-08 19:13 dpdklab
2024-11-08 19:02 dpdklab
2024-11-08 18:52 dpdklab
2024-11-08 18:50 dpdklab
2024-11-08 18:37 dpdklab
2024-11-07 23:40 dpdklab
2024-11-07 21:30 dpdklab
2024-11-07 20:54 dpdklab
2024-11-07 20:00 dpdklab
2024-11-07 19:37 dpdklab
2024-11-07 19:30 dpdklab
2024-11-07 19:03 dpdklab
2024-11-07 19:00 dpdklab
2024-11-07 18:44 dpdklab
2024-11-07 18:35 dpdklab
2024-11-07 18:27 dpdklab
2024-11-07 18:15 dpdklab
2024-11-07 18:15 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=6736a0ba.a70a0220.2418b5.181fSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=jerinj@marvell.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).