From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140308 [PATCH] [v3] test/crypto: fix enqueue dequeue cal
Date: Fri, 24 May 2024 11:57:15 -0700 (PDT) [thread overview]
Message-ID: <6650e30b.630a0220.415d6.6535SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240524171327.885698-1-gakhil@marvell.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140308
_Testing PASS_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Friday, May 24 2024 17:13:27
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6f80df8cb0f889203d7cd27766abcc6ebc720e33
140308 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30007/
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-05-24 18:57 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240524171327.885698-1-gakhil@marvell.com>
2024-05-24 16:47 ` |SUCCESS| pw140308 [PATCH v3] test/crypto: fix enqueue dequeue callback case qemudev
2024-05-24 16:51 ` qemudev
2024-05-24 17:14 ` checkpatch
2024-05-24 18:04 ` 0-day Robot
2024-05-24 18:47 ` |SUCCESS| pw140308 [PATCH] [v3] test/crypto: fix enqueue dequeue cal dpdklab
2024-05-24 18:47 ` dpdklab
2024-05-24 18:47 ` dpdklab
2024-05-24 18:48 ` dpdklab
2024-05-24 18:48 ` dpdklab
2024-05-24 18:48 ` dpdklab
2024-05-24 18:49 ` dpdklab
2024-05-24 18:49 ` dpdklab
2024-05-24 18:49 ` dpdklab
2024-05-24 18:50 ` dpdklab
2024-05-24 18:50 ` dpdklab
2024-05-24 18:50 ` dpdklab
2024-05-24 18:50 ` dpdklab
2024-05-24 18:50 ` dpdklab
2024-05-24 18:51 ` dpdklab
2024-05-24 18:51 ` dpdklab
2024-05-24 18:51 ` dpdklab
2024-05-24 18:52 ` dpdklab
2024-05-24 18:52 ` dpdklab
2024-05-24 18:52 ` dpdklab
2024-05-24 18:52 ` dpdklab
2024-05-24 18:52 ` dpdklab
2024-05-24 18:53 ` dpdklab
2024-05-24 18:53 ` dpdklab
2024-05-24 18:53 ` dpdklab
2024-05-24 18:53 ` dpdklab
2024-05-24 18:54 ` dpdklab
2024-05-24 18:54 ` dpdklab
2024-05-24 18:55 ` dpdklab
2024-05-24 18:55 ` dpdklab
2024-05-24 18:56 ` dpdklab
2024-05-24 18:56 ` dpdklab
2024-05-24 18:56 ` dpdklab
2024-05-24 18:56 ` dpdklab
2024-05-24 18:57 ` dpdklab [this message]
2024-05-24 18:57 ` dpdklab
2024-05-24 18:57 ` dpdklab
2024-05-24 18:57 ` dpdklab
2024-05-24 18:58 ` dpdklab
2024-05-24 18:58 ` dpdklab
2024-05-24 18:58 ` dpdklab
2024-05-24 18:59 ` dpdklab
2024-05-24 18:59 ` dpdklab
2024-05-24 18:59 ` dpdklab
2024-05-24 18:59 ` dpdklab
2024-05-24 18:59 ` dpdklab
2024-05-24 19:00 ` dpdklab
2024-05-24 19:00 ` dpdklab
2024-05-24 19:00 ` dpdklab
2024-05-24 19:00 ` dpdklab
2024-05-24 19:01 ` dpdklab
2024-05-24 19:01 ` dpdklab
2024-05-24 19:01 ` dpdklab
2024-05-24 19:02 ` dpdklab
2024-05-24 19:02 ` dpdklab
2024-05-24 19:02 ` dpdklab
2024-05-24 19:04 ` dpdklab
2024-05-24 19:04 ` dpdklab
2024-05-24 19:05 ` dpdklab
2024-05-24 19:06 ` dpdklab
2024-05-24 19:07 ` dpdklab
2024-05-24 19:07 ` dpdklab
2024-05-24 19:11 ` dpdklab
2024-05-24 19:11 ` dpdklab
2024-05-24 19:11 ` dpdklab
2024-05-24 19:11 ` dpdklab
2024-05-24 19:13 ` dpdklab
2024-05-24 19:14 ` dpdklab
2024-05-24 19:15 ` dpdklab
2024-05-24 19:15 ` dpdklab
2024-05-24 19:15 ` dpdklab
2024-05-24 19:16 ` dpdklab
2024-05-24 19:17 ` dpdklab
2024-05-24 19:18 ` dpdklab
2024-05-24 19:19 ` dpdklab
2024-05-24 19:19 ` dpdklab
2024-05-24 19:22 ` dpdklab
2024-05-24 19:22 ` dpdklab
2024-05-24 19:26 ` dpdklab
2024-05-24 19:28 ` dpdklab
2024-05-24 19:34 ` dpdklab
2024-05-24 20:03 ` dpdklab
2024-05-24 21:29 ` dpdklab
2024-05-28 14:40 ` dpdklab
2024-05-28 14:47 ` 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=6650e30b.630a0220.415d6.6535SMTPIN_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).