From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143647-143643 [PATCH] [v4,7/7] doc: testpmd support even
Date: Thu, 05 Sep 2024 10:35:01 -0700 (PDT) [thread overview]
Message-ID: <66d9ebc5.170a0220.8eff7.1087SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240905092504.10725-8-fengchengwen@huawei.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143643
_Functional Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thursday, September 05 2024 09:25:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:523fd7b3adfdf5a87651e8ca33bc69223b3211d5
143647-143643 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#178576
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 |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| l2fwd | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30916/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-09-05 17:35 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240905092504.10725-8-fengchengwen@huawei.com>
2024-09-05 9:10 ` |SUCCESS| pw143647-143643 [PATCH v4 7/7] doc: testpmd support event handling section qemudev
2024-09-05 9:14 ` qemudev
2024-09-05 9:32 ` |SUCCESS| pw143643 " checkpatch
2024-09-05 10:25 ` 0-day Robot
2024-09-05 17:25 ` |SUCCESS| pw143647-143643 [PATCH] [v4,7/7] doc: testpmd support even dpdklab
2024-09-05 17:26 ` dpdklab
2024-09-05 17:27 ` dpdklab
2024-09-05 17:27 ` dpdklab
2024-09-05 17:27 ` dpdklab
2024-09-05 17:30 ` |PENDING| " dpdklab
2024-09-05 17:31 ` |SUCCESS| " dpdklab
2024-09-05 17:32 ` dpdklab
2024-09-05 17:35 ` dpdklab [this message]
2024-09-05 17:35 ` dpdklab
2024-09-05 17:37 ` |PENDING| " dpdklab
2024-09-05 17:38 ` |SUCCESS| " dpdklab
2024-09-05 17:47 ` dpdklab
2024-09-05 17:48 ` dpdklab
2024-09-05 19:12 ` dpdklab
2024-09-05 19:56 ` dpdklab
2024-09-05 19:56 ` dpdklab
2024-09-05 19:58 ` dpdklab
2024-09-05 19:59 ` dpdklab
2024-09-05 20:01 ` dpdklab
2024-09-05 22:06 ` dpdklab
2024-09-05 22:29 ` dpdklab
2024-09-05 22:32 ` dpdklab
2024-09-05 22:32 ` dpdklab
2024-09-05 22:35 ` dpdklab
2024-09-05 22:40 ` dpdklab
2024-09-05 22:40 ` dpdklab
2024-09-05 22:41 ` dpdklab
2024-09-05 22:42 ` dpdklab
2024-09-05 22:43 ` dpdklab
2024-09-05 22:43 ` dpdklab
2024-09-05 22:45 ` dpdklab
2024-09-05 22:45 ` dpdklab
2024-09-05 22:45 ` dpdklab
2024-09-05 22:47 ` dpdklab
2024-09-05 22:47 ` dpdklab
2024-09-05 22:48 ` dpdklab
2024-09-05 23:00 ` dpdklab
2024-09-05 23:01 ` dpdklab
2024-09-05 23:01 ` dpdklab
2024-09-05 23:01 ` dpdklab
2024-09-05 23:01 ` dpdklab
2024-09-05 23:01 ` dpdklab
2024-09-05 23:02 ` dpdklab
2024-09-05 23:02 ` dpdklab
2024-09-05 23:02 ` dpdklab
2024-09-05 23:02 ` dpdklab
2024-09-05 23:02 ` dpdklab
2024-09-05 23:02 ` dpdklab
2024-09-05 23:44 ` dpdklab
2024-09-07 2:12 ` dpdklab
2024-09-17 23:17 ` dpdklab
2024-09-17 23:36 ` 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=66d9ebc5.170a0220.8eff7.1087SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).