From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw151987-151988 [PATCH] [2/2] net/xsc: suppress assign the
Date: Tue, 25 Feb 2025 15:39:31 -0800 (PST) [thread overview]
Message-ID: <67be54b3.050a0220.c00e3.84a8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250225024813.2489747-3-wanry@yunsilicon.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/151988
_Functional Testing PASS_
Submitter: Renyong Wan <wanry@yunsilicon.com>
Date: Tuesday, February 25 2025 02:48:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a9257af8d8f4f2eb93780a48b53e9342f09ebe9a
151987-151988 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#214297
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 |
+----------------+--------+
| rxtx_callbacks | PASS |
+----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32674/
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:[~2025-02-25 23:39 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250225024813.2489747-3-wanry@yunsilicon.com>
2025-02-25 2:15 ` |SUCCESS| pw151987-151988 [PATCH 2/2] net/xsc: suppress assign the same value warning qemudev
2025-02-25 2:19 ` qemudev
2025-02-25 2:48 ` |SUCCESS| pw151988 " checkpatch
2025-02-25 3:44 ` 0-day Robot
2025-02-25 5:43 ` |SUCCESS| pw151987-151988 [PATCH] [2/2] net/xsc: suppress assign the dpdklab
2025-02-25 5:45 ` dpdklab
2025-02-25 5:45 ` dpdklab
2025-02-25 5:46 ` dpdklab
2025-02-25 5:56 ` |PENDING| " dpdklab
2025-02-25 6:05 ` |SUCCESS| " dpdklab
2025-02-25 6:22 ` dpdklab
2025-02-25 6:52 ` |PENDING| " dpdklab
2025-02-25 7:12 ` dpdklab
2025-02-25 7:29 ` dpdklab
2025-02-25 7:29 ` |SUCCESS| " dpdklab
2025-02-25 7:30 ` dpdklab
2025-02-25 7:54 ` |PENDING| " dpdklab
2025-02-25 8:05 ` |SUCCESS| " dpdklab
2025-02-25 8:05 ` dpdklab
2025-02-25 10:04 ` dpdklab
2025-02-25 11:15 ` dpdklab
2025-02-25 17:07 ` |WARNING| " dpdklab
2025-02-25 23:39 ` dpdklab [this message]
2025-02-26 1:48 ` |SUCCESS| " dpdklab
2025-02-26 1:53 ` dpdklab
2025-02-26 1:57 ` dpdklab
2025-02-26 2:01 ` dpdklab
2025-02-26 2:05 ` dpdklab
2025-02-26 2:30 ` dpdklab
2025-02-26 3:05 ` dpdklab
2025-02-26 3:32 ` |PENDING| " dpdklab
2025-02-26 3:49 ` |SUCCESS| " dpdklab
2025-02-26 4:35 ` dpdklab
2025-02-26 6:31 ` |PENDING| " dpdklab
2025-02-26 6:46 ` dpdklab
2025-02-26 7:20 ` |SUCCESS| " dpdklab
2025-02-26 7:43 ` |PENDING| " dpdklab
2025-02-26 7:46 ` |SUCCESS| " dpdklab
2025-02-26 9:19 ` dpdklab
2025-02-26 9:21 ` dpdklab
2025-02-26 9:29 ` dpdklab
2025-02-26 10:49 ` 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=67be54b3.050a0220.c00e3.84a8SMTPIN_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).