From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw150091 [PATCH] [v1] common/iavf: introduce hardware cloc
Date: Wed, 15 Jan 2025 04:42:58 -0800 (PST) [thread overview]
Message-ID: <6787ad52.050a0220.17c675.3fb7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250115072323.1117429-1-soumyadeep.hore@intel.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/150091
_Functional Testing PASS_
Submitter: Soumyadeep Hore <soumyadeep.hore@intel.com>
Date: Wednesday, January 15 2025 07:23:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ce85dd8562ad9673eb4fe46b4a8bd3a508e8b32f
150091 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#207041
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/32326/
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-15 12:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250115072323.1117429-1-soumyadeep.hore@intel.com>
2025-01-15 8:13 ` |SUCCESS| pw150091 [PATCH v1] common/iavf: introduce hardware clock ID in PTP caps qemudev
2025-01-15 8:17 ` qemudev
2025-01-15 8:39 ` checkpatch
2025-01-15 9:25 ` 0-day Robot
2025-01-15 12:16 ` |SUCCESS| pw150091 [PATCH] [v1] common/iavf: introduce hardware cloc dpdklab
2025-01-15 12:25 ` dpdklab
2025-01-15 12:30 ` dpdklab
2025-01-15 12:42 ` dpdklab [this message]
2025-01-15 12:46 ` dpdklab
2025-01-15 12:53 ` dpdklab
2025-01-15 13:04 ` dpdklab
2025-01-15 13:09 ` dpdklab
2025-01-15 13:18 ` dpdklab
2025-01-15 13:23 ` |PENDING| " dpdklab
2025-01-15 13:44 ` |SUCCESS| " dpdklab
2025-01-15 13:48 ` dpdklab
2025-01-15 13:52 ` dpdklab
2025-01-15 14:17 ` dpdklab
2025-01-15 14:34 ` dpdklab
2025-01-15 14:44 ` |WARNING| " dpdklab
2025-01-15 15:26 ` |SUCCESS| " 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=6787ad52.050a0220.17c675.3fb7SMTPIN_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).