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| pw141512-141523 [PATCH] [v2,12/12] crypto/cnxk: enable dua
Date: Mon, 24 Jun 2024 05:34:01 -0700 (PDT)	[thread overview]
Message-ID: <667967b9.920a0220.68a6d.aec3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240624062401.4143606-13-asasidharan@marvell.com>

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

_Testing PASS_

Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Monday, June 24 2024 06:24:01 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f

141512-141523 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| FreeBSD 13.3        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+


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

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

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/30284/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-24 12:34 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240624062401.4143606-13-asasidharan@marvell.com>
2024-06-24  6:06 ` |SUCCESS| pw141512-141523 [PATCH v2 12/12] crypto/cnxk: enable dual submission to CPT qemudev
2024-06-24  6:10 ` qemudev
2024-06-24  6:34 ` |SUCCESS| pw141523 " checkpatch
2024-06-24  7:24 ` 0-day Robot
2024-06-24 10:40 ` |SUCCESS| pw141512-141523 [PATCH] [v2,12/12] crypto/cnxk: enable dua dpdklab
2024-06-24 10:43 ` dpdklab
2024-06-24 10:44 ` dpdklab
2024-06-24 10:51 ` dpdklab
2024-06-24 10:51 ` dpdklab
2024-06-24 10:54 ` dpdklab
2024-06-24 10:55 ` dpdklab
2024-06-24 11:28 ` dpdklab
2024-06-24 11:28 ` dpdklab
2024-06-24 11:28 ` dpdklab
2024-06-24 11:32 ` dpdklab
2024-06-24 11:33 ` dpdklab
2024-06-24 11:33 ` dpdklab
2024-06-24 11:34 ` dpdklab
2024-06-24 11:35 ` dpdklab
2024-06-24 11:36 ` dpdklab
2024-06-24 11:40 ` dpdklab
2024-06-24 12:28 ` dpdklab
2024-06-24 12:29 ` dpdklab
2024-06-24 12:30 ` dpdklab
2024-06-24 12:31 ` dpdklab
2024-06-24 12:32 ` dpdklab
2024-06-24 12:32 ` dpdklab
2024-06-24 12:33 ` dpdklab
2024-06-24 12:34 ` dpdklab [this message]
2024-06-24 12:34 ` dpdklab
2024-06-24 12:35 ` dpdklab
2024-06-24 12:47 ` dpdklab
2024-06-24 12:48 ` dpdklab
2024-06-24 12:48 ` dpdklab
2024-06-24 12:48 ` dpdklab
2024-06-24 12:49 ` dpdklab
2024-06-24 12:50 ` dpdklab
2024-06-24 12:50 ` dpdklab
2024-06-24 12:52 ` dpdklab
2024-06-24 13:06 ` dpdklab
2024-06-24 13:06 ` dpdklab
2024-06-24 13:09 ` dpdklab
2024-06-24 13:10 ` dpdklab
2024-06-24 13:12 ` dpdklab
2024-06-24 13:13 ` dpdklab
2024-06-24 13:15 ` dpdklab
2024-06-24 13:17 ` dpdklab
2024-06-24 13:18 ` dpdklab
2024-06-24 13:19 ` dpdklab
2024-06-24 13:20 ` dpdklab
2024-06-24 13:20 ` dpdklab
2024-06-24 13:20 ` dpdklab
2024-06-24 13:21 ` dpdklab
2024-06-24 13:23 ` dpdklab
2024-06-24 13:23 ` dpdklab
2024-06-24 13:25 ` dpdklab
2024-06-24 13:28 ` dpdklab
2024-06-24 13:28 ` dpdklab
2024-06-24 13:49 ` dpdklab
2024-06-24 13:50 ` dpdklab
2024-06-24 13:50 ` dpdklab
2024-06-24 13:51 ` dpdklab
2024-06-24 13:52 ` dpdklab
2024-06-24 13:52 ` dpdklab
2024-06-24 14:07 ` dpdklab
2024-06-24 14:10 ` dpdklab
2024-06-24 14:11 ` dpdklab
2024-06-24 14:12 ` dpdklab
2024-06-24 14:12 ` dpdklab
2024-06-24 14:14 ` dpdklab
2024-06-24 14:15 ` dpdklab
2024-06-24 14:15 ` dpdklab
2024-06-24 14:16 ` dpdklab
2024-06-24 14:17 ` dpdklab
2024-06-24 14:19 ` dpdklab
2024-06-24 14:23 ` dpdklab
2024-06-24 14:23 ` dpdklab
2024-06-24 14:23 ` dpdklab
2024-06-24 14:23 ` dpdklab
2024-06-24 14:23 ` dpdklab
2024-06-24 14:24 ` dpdklab
2024-06-24 14:24 ` dpdklab
2024-06-24 14:25 ` dpdklab
2024-06-24 14:25 ` dpdklab
2024-06-24 14:26 ` dpdklab
2024-06-24 14:26 ` dpdklab
2024-06-24 14:27 ` dpdklab
2024-06-24 14:29 ` dpdklab
2024-06-24 14:29 ` dpdklab
2024-06-24 14:30 ` dpdklab
2024-06-24 14:30 ` dpdklab
2024-06-24 14:31 ` dpdklab
2024-06-24 14:33 ` dpdklab
2024-06-24 14:33 ` dpdklab
2024-06-24 14:33 ` dpdklab
2024-06-24 14:34 ` dpdklab
2024-06-24 14:34 ` dpdklab
2024-06-24 14:35 ` dpdklab
2024-06-24 14:35 ` dpdklab
2024-06-24 14:36 ` dpdklab
2024-06-24 14:38 ` dpdklab
2024-06-24 14:41 ` dpdklab
2024-06-24 14:47 ` dpdklab
2024-06-24 14:48 ` dpdklab
2024-06-24 14:51 ` dpdklab
2024-06-24 15:18 ` dpdklab
2024-06-24 15:18 ` dpdklab
2024-06-24 15:19 ` dpdklab
2024-06-24 15:26 ` dpdklab
2024-06-24 15:27 ` dpdklab
2024-06-24 15:33 ` dpdklab
2024-06-24 15:35 ` dpdklab
2024-06-24 15:56 ` dpdklab
2024-06-24 15:56 ` dpdklab
2024-06-24 15:58 ` dpdklab
2024-06-24 18:15 ` 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=667967b9.920a0220.68a6d.aec3SMTPIN_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).