From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw145757 [PATCH] [v6,1/1] dmadev: support strict priority
Date: Fri, 11 Oct 2024 13:27:57 -0700 (PDT) [thread overview]
Message-ID: <67098a4d.170a0220.14e1d1.52cfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241011101236.1467783-1-vattunuru@marvell.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/145757
_Testing PASS_
Submitter: Vamsi Krishna <vattunuru@marvell.com>
Date: Friday, October 11 2024 10:12:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:672c32999e18d7194de90d12d3166c1a967dcb44
145757 --> testing pass
Upstream job id: Generic-VM-Unit-Test-DPDK#25625
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS |
+---------------------+----------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31432/
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-10-11 20:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241011101236.1467783-1-vattunuru@marvell.com>
2024-10-11 9:45 ` |SUCCESS| pw145757 [PATCH v6 1/1] dmadev: support strict priority configuration qemudev
2024-10-11 9:49 ` qemudev
2024-10-11 10:13 ` checkpatch
2024-10-11 11:03 ` 0-day Robot
2024-10-11 18:32 ` |SUCCESS| pw145757 [PATCH] [v6,1/1] dmadev: support strict priority dpdklab
2024-10-11 18:33 ` dpdklab
2024-10-11 19:03 ` dpdklab
2024-10-11 19:06 ` dpdklab
2024-10-11 20:05 ` dpdklab
2024-10-11 20:17 ` dpdklab
2024-10-11 20:27 ` dpdklab [this message]
2024-10-11 21:01 ` |PENDING| " dpdklab
2024-10-11 21:25 ` |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=67098a4d.170a0220.14e1d1.52cfSMTPIN_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).