From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152849 [PATCH] [v1] net/zxdh: fix using static assert in
Date: Wed, 09 Apr 2025 00:00:53 -0700 (PDT) [thread overview]
Message-ID: <67f61b25.050a0220.38a5aa.15e5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250409013955.133122-1-wang.junlong1@zte.com.cn>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152849
_Functional Testing PASS_
Submitter: Junlong Wang <wang.junlong1@zte.com.cn>
Date: Wednesday, April 09 2025 01:39:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0b2f016cd76d4fb382eea54b8a6aaf9474586fbc
152849 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#220918
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/32976/
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-04-09 7:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250409013955.133122-1-wang.junlong1@zte.com.cn>
2025-04-09 1:07 ` |SUCCESS| pw152849 [PATCH v1] net/zxdh: fix using static assert in macro definition qemudev
2025-04-09 1:11 ` qemudev
2025-04-09 1:41 ` checkpatch
2025-04-09 7:00 ` dpdklab [this message]
2025-04-09 7:03 ` |SUCCESS| pw152849 [PATCH] [v1] net/zxdh: fix using static assert in dpdklab
2025-04-09 7:10 ` dpdklab
2025-04-09 7:16 ` |PENDING| " dpdklab
2025-04-09 7:22 ` |SUCCESS| " dpdklab
2025-04-09 7:22 ` dpdklab
2025-04-09 7:23 ` dpdklab
2025-04-09 7:23 ` dpdklab
2025-04-09 7:37 ` dpdklab
2025-04-09 7:38 ` |PENDING| " dpdklab
2025-04-09 7:44 ` dpdklab
2025-04-09 8:02 ` |SUCCESS| " dpdklab
2025-04-09 8:23 ` dpdklab
2025-04-09 8:32 ` dpdklab
2025-04-09 8:58 ` |PENDING| " dpdklab
2025-04-09 9:08 ` dpdklab
2025-04-09 9:44 ` |SUCCESS| " dpdklab
2025-04-09 9:51 ` dpdklab
2025-04-09 9:59 ` dpdklab
2025-04-09 10:48 ` dpdklab
2025-04-09 10:50 ` dpdklab
2025-04-09 11:03 ` dpdklab
2025-04-09 14:06 ` dpdklab
2025-04-09 14:38 ` dpdklab
2025-04-09 18:02 ` dpdklab
2025-04-10 22:34 ` dpdklab
2025-04-10 22:38 ` 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=67f61b25.050a0220.38a5aa.15e5SMTPIN_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).