automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144100-144102 [PATCH] [v2,3/3] eventdev: add SW event pr
Date: Tue, 17 Sep 2024 02:13:54 -0700 (PDT)	[thread overview]
Message-ID: <66e94852.050a0220.2267c7.d2afSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240917071106.8815-4-pbhagavatula@marvell.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/144102

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tuesday, September 17 2024 07:11:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

144100-144102 --> testing pass

Upstream job id: Windows-Compile-DPDK-Native#22269

Test environment and result as below:

+---------------------+----------------------+-----------------------+--------------------+
|     Environment     | dpdk_mingw64_compile | dpdk_win_llvm_compile | dpdk_meson_compile |
+=====================+======================+=======================+====================+
| Windows Server 2022 | PASS                 | PASS                  | SKIPPED            |
+---------------------+----------------------+-----------------------+--------------------+
| FreeBSD 13.3        | SKIPPED              | SKIPPED               | PASS               |
+---------------------+----------------------+-----------------------+--------------------+
| FreeBSD 14.1        | SKIPPED              | SKIPPED               | 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

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p5
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31042/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-09-17  9:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240917071106.8815-4-pbhagavatula@marvell.com>
2024-09-17  6:44 ` |SUCCESS| pw144100-144102 [PATCH v2 3/3] eventdev: add SW event preschedule hint qemudev
2024-09-17  6:48 ` qemudev
2024-09-17  7:12 ` |SUCCESS| pw144102 " checkpatch
2024-09-17  8:04 ` 0-day Robot
2024-09-17  8:53 ` |SUCCESS| pw144100-144102 [PATCH] [v2,3/3] eventdev: add SW event pr dpdklab
2024-09-17  9:04 ` |PENDING| " dpdklab
2024-09-17  9:13 ` dpdklab [this message]
2024-09-17  9:14 ` |SUCCESS| " dpdklab
2024-09-17  9:16 ` dpdklab
2024-09-17  9:22 ` dpdklab
2024-09-17  9:29 ` dpdklab
2024-09-17  9:47 ` dpdklab
2024-09-17  9:52 ` dpdklab
2024-09-17 10:39 ` |PENDING| " dpdklab
2024-09-17 11:10 ` dpdklab
2024-09-17 11:54 ` dpdklab
2024-09-17 12:21 ` |SUCCESS| " dpdklab
2024-09-17 12:22 ` dpdklab
2024-09-17 12:29 ` dpdklab
2024-09-17 12:40 ` dpdklab
2024-09-17 12:44 ` dpdklab
2024-09-17 13:02 ` dpdklab
2024-09-17 14:32 ` dpdklab
2024-09-17 20:27 ` dpdklab
2024-09-17 21:49 ` dpdklab
2024-09-22  3:05 ` dpdklab
2024-09-22  3:16 ` 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=66e94852.050a0220.2267c7.d2afSMTPIN_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).