From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw150141-150142 [PATCH] [v2,2/2] ethdev: fix some function
Date: Thu, 16 Jan 2025 05:18:15 -0800 (PST) [thread overview]
Message-ID: <67890717.170a0220.7ccd6.04bcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250116114034.9858-3-lihuisong@huawei.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/150142
_Functional Testing PASS_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Thursday, January 16 2025 11:40:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:167adc84d05c732af3c47dd569f152fa4ba234d6
150141-150142 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#207313
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 |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32342/
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-01-16 13:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250116114034.9858-3-lihuisong@huawei.com>
2025-01-16 11:27 ` |SUCCESS| pw150141-150142 [PATCH v2 2/2] ethdev: fix some functions are available in the new event qemudev
2025-01-16 11:32 ` qemudev
2025-01-16 11:53 ` |SUCCESS| pw150142 " checkpatch
2025-01-16 12:45 ` 0-day Robot
2025-01-16 12:57 ` |SUCCESS| pw150141-150142 [PATCH] [v2,2/2] ethdev: fix some function dpdklab
2025-01-16 12:57 ` dpdklab
2025-01-16 13:03 ` dpdklab
2025-01-16 13:05 ` |PENDING| " dpdklab
2025-01-16 13:06 ` dpdklab
2025-01-16 13:06 ` dpdklab
2025-01-16 13:09 ` |SUCCESS| " dpdklab
2025-01-16 13:10 ` dpdklab
2025-01-16 13:12 ` dpdklab
2025-01-16 13:13 ` dpdklab
2025-01-16 13:16 ` dpdklab
2025-01-16 13:18 ` dpdklab [this message]
2025-01-16 13:25 ` dpdklab
2025-01-16 13:53 ` dpdklab
2025-01-16 13:53 ` dpdklab
2025-01-16 14:17 ` dpdklab
2025-01-16 14:31 ` |WARNING| " dpdklab
2025-01-16 14:31 ` |SUCCESS| " dpdklab
2025-01-16 16:05 ` 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=67890717.170a0220.7ccd6.04bcSMTPIN_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).