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| pw141582-141589 [PATCH] [v2,9/9] test/bbdev: remove unnece
Date: Mon, 24 Jun 2024 19:48:47 -0700 (PDT)	[thread overview]
Message-ID: <667a300f.050a0220.e9fb5.678eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240624150237.47169-10-hernan.vargas@intel.com>

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

_Testing PASS_

Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Monday, June 24 2024 15:02:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:bd4f4bb29a6e6f07ff535669b8d0b5094e3d5265

141582-141589 --> 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/30299/

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-25  2:48 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240624150237.47169-10-hernan.vargas@intel.com>
2024-06-24 14:41 ` |SUCCESS| pw141582-141589 [PATCH v2 9/9] test/bbdev: remove unnecessary line qemudev
2024-06-24 14:46 ` qemudev
2024-06-24 15:08 ` |WARNING| pw141589 " checkpatch
2024-06-24 16:04 ` |SUCCESS| " 0-day Robot
2024-06-25  0:19 ` |SUCCESS| pw141582-141589 [PATCH] [v2,9/9] test/bbdev: remove unnece dpdklab
2024-06-25  0:21 ` dpdklab
2024-06-25  0:24 ` dpdklab
2024-06-25  0:25 ` dpdklab
2024-06-25  0:30 ` dpdklab
2024-06-25  0:31 ` dpdklab
2024-06-25  0:33 ` dpdklab
2024-06-25  0:33 ` dpdklab
2024-06-25  0:36 ` dpdklab
2024-06-25  0:38 ` dpdklab
2024-06-25  0:40 ` dpdklab
2024-06-25  0:41 ` dpdklab
2024-06-25  1:01 ` dpdklab
2024-06-25  1:03 ` dpdklab
2024-06-25  1:19 ` dpdklab
2024-06-25  1:30 ` dpdklab
2024-06-25  1:56 ` dpdklab
2024-06-25  2:16 ` dpdklab
2024-06-25  2:17 ` dpdklab
2024-06-25  2:17 ` dpdklab
2024-06-25  2:19 ` dpdklab
2024-06-25  2:19 ` dpdklab
2024-06-25  2:20 ` dpdklab
2024-06-25  2:20 ` dpdklab
2024-06-25  2:20 ` dpdklab
2024-06-25  2:21 ` dpdklab
2024-06-25  2:26 ` dpdklab
2024-06-25  2:28 ` dpdklab
2024-06-25  2:29 ` dpdklab
2024-06-25  2:31 ` dpdklab
2024-06-25  2:44 ` dpdklab
2024-06-25  2:46 ` dpdklab
2024-06-25  2:47 ` dpdklab
2024-06-25  2:48 ` dpdklab [this message]
2024-06-25  3:16 ` dpdklab
2024-06-25  3:29 ` dpdklab
2024-06-25  3:37 ` dpdklab
2024-06-25  3:38 ` dpdklab
2024-06-25  3:39 ` dpdklab
2024-06-25  3:40 ` dpdklab
2024-06-25  3:41 ` dpdklab
2024-06-25  3:42 ` dpdklab
2024-06-25  3:43 ` dpdklab
2024-06-25  3:44 ` dpdklab
2024-06-25  3:45 ` dpdklab
2024-06-25  3:46 ` dpdklab
2024-06-25  3:46 ` dpdklab
2024-06-25  3:46 ` dpdklab
2024-06-25  3:46 ` dpdklab
2024-06-25  3:48 ` dpdklab
2024-06-25  3:54 ` dpdklab
2024-06-25  3:55 ` dpdklab
2024-06-25  3:55 ` dpdklab
2024-06-25  3:55 ` dpdklab
2024-06-25  4:11 ` dpdklab
2024-06-25  4:14 ` dpdklab
2024-06-25  4:14 ` dpdklab
2024-06-25  4:15 ` dpdklab
2024-06-25  4:15 ` dpdklab
2024-06-25  4:15 ` dpdklab
2024-06-25  4:16 ` dpdklab
2024-06-25  4:16 ` dpdklab
2024-06-25  4:16 ` dpdklab
2024-06-25  4:17 ` dpdklab
2024-06-25  4:19 ` dpdklab
2024-06-25  4:19 ` dpdklab
2024-06-25  4:20 ` dpdklab
2024-06-25  4:20 ` dpdklab
2024-06-25  4:22 ` dpdklab
2024-06-25  4:22 ` dpdklab
2024-06-25  4:23 ` dpdklab
2024-06-25  4:26 ` dpdklab
2024-06-25  4:26 ` dpdklab
2024-06-25  4:27 ` dpdklab
2024-06-25  4:27 ` dpdklab
2024-06-25  4:28 ` dpdklab
2024-06-25  4:28 ` dpdklab
2024-06-25  4:28 ` dpdklab
2024-06-25  4:29 ` dpdklab
2024-06-25  4:30 ` dpdklab
2024-06-25  4:31 ` dpdklab
2024-06-25  4:31 ` dpdklab
2024-06-25  4:44 ` dpdklab
2024-06-25  5:03 ` dpdklab
2024-06-25  5:03 ` dpdklab
2024-06-25  5:03 ` dpdklab
2024-06-25  5:04 ` dpdklab
2024-06-25  5:05 ` dpdklab
2024-06-25  5:06 ` dpdklab
2024-06-25  5:06 ` dpdklab
2024-06-25  5:10 ` dpdklab
2024-06-25  5:11 ` dpdklab
2024-06-25  5:15 ` dpdklab
2024-06-25  5:20 ` dpdklab
2024-06-25  5:22 ` dpdklab
2024-06-25  5:31 ` dpdklab
2024-06-25  5:32 ` dpdklab
2024-06-25  5:33 ` dpdklab
2024-06-25  5:35 ` dpdklab
2024-06-25  5:36 ` dpdklab
2024-06-25  5:37 ` dpdklab
2024-06-25  6:05 ` dpdklab
2024-06-25  6:10 ` dpdklab
2024-06-25  6:16 ` dpdklab
2024-06-25  6:19 ` dpdklab
2024-06-25  6:59 ` dpdklab
2024-06-25  7:34 ` dpdklab
2024-06-25  8:14 ` dpdklab
2024-06-25  8:20 ` dpdklab
2024-06-25  8:48 ` dpdklab
2024-06-25  9:16 ` dpdklab
2024-06-25 16:52 ` 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=667a300f.050a0220.e9fb5.678eSMTPIN_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).