From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141485-141486 [PATCH] [v3,2/2] eventdev: add support for
Date: Fri, 21 Jun 2024 16:34:07 -0700 (PDT) [thread overview]
Message-ID: <66760def.050a0220.524c.2e73SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240621222408.583464-3-abdullah.sevincer@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141486
_Testing PASS_
Submitter: Abdullah Sevincer <abdullah.sevincer@intel.com>
Date: Friday, June 21 2024 22:24:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f
141485-141486 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2022 | PASS | PASS | PASS |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS | PASS | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
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
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30275/
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-06-21 23:34 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240621222408.583464-3-abdullah.sevincer@intel.com>
2024-06-21 22:02 ` |SUCCESS| pw141485-141486 [PATCH v3 2/2] eventdev: add support for enqueue reorder qemudev
2024-06-21 22:06 ` qemudev
2024-06-21 22:25 ` |SUCCESS| pw141486 " checkpatch
2024-06-21 23:16 ` |SUCCESS| pw141485-141486 [PATCH] [v3,2/2] eventdev: add support for dpdklab
2024-06-21 23:17 ` dpdklab
2024-06-21 23:17 ` dpdklab
2024-06-21 23:17 ` dpdklab
2024-06-21 23:18 ` dpdklab
2024-06-21 23:18 ` dpdklab
2024-06-21 23:23 ` dpdklab
2024-06-21 23:24 ` |FAILURE| pw141486 [PATCH v3 2/2] eventdev: add support for enqueue reorder 0-day Robot
2024-06-21 23:27 ` |SUCCESS| pw141485-141486 [PATCH] [v3,2/2] eventdev: add support for dpdklab
2024-06-21 23:28 ` dpdklab
2024-06-21 23:28 ` dpdklab
2024-06-21 23:29 ` dpdklab
2024-06-21 23:29 ` dpdklab
2024-06-21 23:30 ` dpdklab
2024-06-21 23:30 ` dpdklab
2024-06-21 23:31 ` dpdklab
2024-06-21 23:31 ` dpdklab
2024-06-21 23:32 ` dpdklab
2024-06-21 23:32 ` dpdklab
2024-06-21 23:32 ` dpdklab
2024-06-21 23:33 ` dpdklab
2024-06-21 23:34 ` dpdklab [this message]
2024-06-21 23:34 ` dpdklab
2024-06-21 23:34 ` dpdklab
2024-06-21 23:35 ` dpdklab
2024-06-21 23:36 ` dpdklab
2024-06-21 23:37 ` dpdklab
2024-06-21 23:44 ` dpdklab
2024-06-21 23:45 ` dpdklab
2024-06-21 23:45 ` dpdklab
2024-06-21 23:45 ` dpdklab
2024-06-21 23:45 ` dpdklab
2024-06-21 23:46 ` dpdklab
2024-06-21 23:46 ` dpdklab
2024-06-21 23:47 ` dpdklab
2024-06-21 23:47 ` dpdklab
2024-06-21 23:47 ` dpdklab
2024-06-21 23:48 ` dpdklab
2024-06-21 23:48 ` dpdklab
2024-06-21 23:48 ` dpdklab
2024-06-21 23:49 ` dpdklab
2024-06-21 23:49 ` dpdklab
2024-06-21 23:49 ` dpdklab
2024-06-21 23:50 ` dpdklab
2024-06-21 23:51 ` dpdklab
2024-06-21 23:51 ` dpdklab
2024-06-21 23:51 ` dpdklab
2024-06-21 23:51 ` dpdklab
2024-06-21 23:52 ` dpdklab
2024-06-21 23:52 ` |FAILURE| " dpdklab
2024-06-21 23:52 ` dpdklab
2024-06-21 23:52 ` |SUCCESS| " dpdklab
2024-06-21 23:53 ` dpdklab
2024-06-21 23:53 ` dpdklab
2024-06-21 23:53 ` dpdklab
2024-06-21 23:53 ` dpdklab
2024-06-21 23:54 ` dpdklab
2024-06-21 23:54 ` |FAILURE| " dpdklab
2024-06-21 23:54 ` |SUCCESS| " dpdklab
2024-06-21 23:54 ` |FAILURE| " dpdklab
2024-06-21 23:55 ` dpdklab
2024-06-21 23:55 ` |SUCCESS| " dpdklab
2024-06-21 23:55 ` |FAILURE| " dpdklab
2024-06-21 23:56 ` dpdklab
2024-06-21 23:56 ` |SUCCESS| " dpdklab
2024-06-21 23:56 ` |FAILURE| " dpdklab
2024-06-21 23:56 ` dpdklab
2024-06-21 23:56 ` dpdklab
2024-06-21 23:57 ` dpdklab
2024-06-21 23:57 ` dpdklab
2024-06-21 23:57 ` dpdklab
2024-06-21 23:58 ` |SUCCESS| " dpdklab
2024-06-22 0:15 ` |FAILURE| " dpdklab
2024-06-22 0:16 ` dpdklab
2024-06-22 0:16 ` dpdklab
2024-06-22 0:16 ` dpdklab
2024-06-22 0:16 ` dpdklab
2024-06-22 0:17 ` dpdklab
2024-06-22 0:17 ` dpdklab
2024-06-22 0:18 ` dpdklab
2024-06-22 0:18 ` dpdklab
2024-06-22 0:18 ` |SUCCESS| " dpdklab
2024-06-22 0:19 ` |FAILURE| " dpdklab
2024-06-22 0:19 ` dpdklab
2024-06-22 0:19 ` dpdklab
2024-06-22 0:19 ` dpdklab
2024-06-22 0:20 ` dpdklab
2024-06-22 0:20 ` dpdklab
2024-06-22 0:20 ` |SUCCESS| " dpdklab
2024-06-22 0:21 ` |FAILURE| " dpdklab
2024-06-22 0:22 ` |SUCCESS| " dpdklab
2024-06-22 0:28 ` |FAILURE| " dpdklab
2024-06-22 0:29 ` |SUCCESS| " dpdklab
2024-06-22 0:30 ` dpdklab
2024-06-22 0:30 ` dpdklab
2024-06-22 0:31 ` dpdklab
2024-06-22 0:33 ` dpdklab
2024-06-22 0:46 ` dpdklab
2024-06-22 0:46 ` dpdklab
2024-06-22 0:46 ` dpdklab
2024-06-22 0:47 ` dpdklab
2024-06-22 0:48 ` dpdklab
2024-06-22 0:49 ` |FAILURE| " dpdklab
2024-06-22 1:17 ` |SUCCESS| " dpdklab
2024-06-22 1:18 ` dpdklab
2024-06-22 1:18 ` dpdklab
2024-06-22 1:20 ` dpdklab
2024-06-22 1:22 ` dpdklab
2024-06-22 1:41 ` dpdklab
2024-06-22 1:42 ` dpdklab
2024-06-22 1:42 ` dpdklab
2024-06-22 1:45 ` dpdklab
2024-06-22 2:29 ` dpdklab
2024-06-22 2:36 ` dpdklab
2024-06-22 13:23 ` 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=66760def.050a0220.524c.2e73SMTPIN_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).