From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142063-142073 [PATCH] [11/11] crypto/dpaa2_sec: fix issu
Date: Thu, 04 Jul 2024 15:51:15 -0700 (PDT) [thread overview]
Message-ID: <66872763.050a0220.14e2.a674SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240703102649.3096530-12-g.singh@nxp.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/142073
_Testing PASS_
Submitter: Gagandeep Singh <g.singh@nxp.com>
Date: Wednesday, July 03 2024 10:26:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:95bea772528d316c969a170e6206f3b05ac39413
142063-142073 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | PASS |
+---------------------+--------------------+----------------------+
| FreeBSD 13.3 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 14.1 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30398/
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-07-04 22:51 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240703102649.3096530-12-g.singh@nxp.com>
2024-07-03 10:02 ` |SUCCESS| pw142063-142073 [PATCH 11/11] crypto/dpaa2_sec: fix issue of user ctxt for Event queue qemudev
2024-07-03 10:06 ` qemudev
2024-07-03 10:29 ` |SUCCESS| pw142073 " checkpatch
2024-07-03 11:24 ` 0-day Robot
2024-07-04 9:01 ` |SUCCESS| pw142063-142073 [PATCH] [11/11] crypto/dpaa2_sec: fix issu dpdklab
2024-07-04 9:03 ` dpdklab
2024-07-04 9:12 ` dpdklab
2024-07-04 9:15 ` dpdklab
2024-07-04 9:16 ` dpdklab
2024-07-04 9:25 ` dpdklab
2024-07-04 10:00 ` dpdklab
2024-07-04 12:17 ` |PENDING| " dpdklab
2024-07-04 12:26 ` dpdklab
2024-07-04 12:29 ` dpdklab
2024-07-04 12:31 ` dpdklab
2024-07-04 12:32 ` dpdklab
2024-07-04 12:35 ` dpdklab
2024-07-04 12:35 ` dpdklab
2024-07-04 12:37 ` dpdklab
2024-07-04 12:38 ` dpdklab
2024-07-04 12:39 ` dpdklab
2024-07-04 12:40 ` dpdklab
2024-07-04 12:46 ` dpdklab
2024-07-04 12:46 ` dpdklab
2024-07-04 12:51 ` dpdklab
2024-07-04 12:54 ` |SUCCESS| " dpdklab
2024-07-04 12:55 ` dpdklab
2024-07-04 13:05 ` dpdklab
2024-07-04 14:33 ` dpdklab
2024-07-04 14:37 ` dpdklab
2024-07-04 14:42 ` dpdklab
2024-07-04 14:47 ` dpdklab
2024-07-04 15:06 ` dpdklab
2024-07-04 15:58 ` dpdklab
2024-07-04 16:06 ` dpdklab
2024-07-04 16:41 ` dpdklab
2024-07-04 22:46 ` |PENDING| " dpdklab
2024-07-04 22:46 ` dpdklab
2024-07-04 22:47 ` dpdklab
2024-07-04 22:51 ` dpdklab [this message]
2024-07-04 22:52 ` |SUCCESS| " dpdklab
2024-07-04 23:30 ` dpdklab
2024-07-05 0:30 ` |PENDING| " dpdklab
2024-07-05 1:37 ` dpdklab
2024-07-05 1:41 ` dpdklab
2024-07-05 3:28 ` dpdklab
2024-07-05 4:28 ` dpdklab
2024-07-05 5:45 ` dpdklab
2024-07-05 6:04 ` dpdklab
2024-07-05 6:09 ` dpdklab
2024-07-05 6:28 ` dpdklab
2024-07-05 6:45 ` dpdklab
2024-07-05 8:12 ` dpdklab
2024-07-05 8:13 ` dpdklab
2024-07-05 8:20 ` dpdklab
2024-07-05 8:23 ` dpdklab
2024-07-05 8:26 ` dpdklab
2024-07-05 8:30 ` |SUCCESS| " dpdklab
2024-07-05 8:30 ` dpdklab
2024-07-05 8:30 ` dpdklab
2024-07-05 8:31 ` |PENDING| " dpdklab
2024-07-05 8:32 ` |SUCCESS| " dpdklab
2024-07-05 8:32 ` |PENDING| " dpdklab
2024-07-05 8:39 ` dpdklab
2024-07-05 8:40 ` dpdklab
2024-07-05 8:48 ` dpdklab
2024-07-05 9:11 ` dpdklab
2024-07-05 9:20 ` dpdklab
2024-07-05 9:21 ` dpdklab
2024-07-05 9:28 ` dpdklab
2024-07-05 9:34 ` dpdklab
2024-07-05 9:36 ` dpdklab
2024-07-05 9:37 ` dpdklab
2024-07-05 9:37 ` dpdklab
2024-07-05 9:39 ` dpdklab
2024-07-05 9:44 ` dpdklab
2024-07-05 9:44 ` dpdklab
2024-07-05 9:46 ` dpdklab
2024-07-05 9:47 ` dpdklab
2024-07-05 9:47 ` dpdklab
2024-07-05 9:49 ` dpdklab
2024-07-05 9:51 ` dpdklab
2024-07-05 9:52 ` dpdklab
2024-07-05 9:55 ` dpdklab
2024-07-05 9:55 ` dpdklab
2024-07-05 9:55 ` |SUCCESS| " dpdklab
2024-07-05 9:56 ` dpdklab
2024-07-05 9:57 ` |PENDING| " dpdklab
2024-07-05 9:58 ` dpdklab
2024-07-05 9:59 ` dpdklab
2024-07-05 10:06 ` dpdklab
2024-07-05 10:07 ` dpdklab
2024-07-05 10:08 ` dpdklab
2024-07-05 10:11 ` dpdklab
2024-07-05 10:12 ` dpdklab
2024-07-05 10:12 ` dpdklab
2024-07-05 10:15 ` |SUCCESS| " dpdklab
2024-07-05 10:16 ` dpdklab
2024-07-05 10:22 ` |PENDING| " dpdklab
2024-07-05 10:26 ` dpdklab
2024-07-05 10:27 ` dpdklab
2024-07-05 10:32 ` dpdklab
2024-07-05 10:38 ` dpdklab
2024-07-05 10:47 ` dpdklab
2024-07-05 11:12 ` dpdklab
2024-07-05 11:21 ` dpdklab
2024-07-05 11:21 ` dpdklab
2024-07-05 11:29 ` dpdklab
2024-07-05 11:58 ` dpdklab
2024-07-05 12:02 ` |SUCCESS| " dpdklab
2024-07-05 12:03 ` dpdklab
2024-07-05 23:43 ` dpdklab
2024-07-06 8:25 ` dpdklab
2024-07-06 9:33 ` 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=66872763.050a0220.14e2.a674SMTPIN_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).