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| pw142968 [PATCH] [v2] dts: add flow rule dataclass to test
Date: Tue, 06 Aug 2024 12:12:43 -0700 (PDT)	[thread overview]
Message-ID: <66b275ab.050a0220.118338.1d4eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240806164208.3351-1-dmarx@iol.unh.edu>

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

_Testing PASS_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Tuesday, August 06 2024 16:42:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

142968 --> testing pass

Upstream job id: Windows-Compile-DPDK-Meson#24137

Test environment and result as below:

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


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)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-06 19:12 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240806164208.3351-1-dmarx@iol.unh.edu>
2024-08-06 16:16 ` |SUCCESS| pw142968 [PATCH v2] dts: add flow rule dataclass to testpmd shell qemudev
2024-08-06 16:20 ` qemudev
2024-08-06 16:42 ` checkpatch
2024-08-06 17:43 ` 0-day Robot
2024-08-06 18:25 ` |PENDING| pw142968 [PATCH] [v2] dts: add flow rule dataclass to test dpdklab
2024-08-06 18:27 ` dpdklab
2024-08-06 18:28 ` dpdklab
2024-08-06 18:28 ` |SUCCESS| " dpdklab
2024-08-06 18:28 ` |PENDING| " dpdklab
2024-08-06 18:30 ` dpdklab
2024-08-06 18:30 ` dpdklab
2024-08-06 18:33 ` |SUCCESS| " dpdklab
2024-08-06 18:33 ` |PENDING| " dpdklab
2024-08-06 18:43 ` |SUCCESS| " dpdklab
2024-08-06 18:46 ` dpdklab
2024-08-06 18:47 ` |PENDING| " dpdklab
2024-08-06 18:48 ` |SUCCESS| " dpdklab
2024-08-06 18:51 ` |PENDING| " dpdklab
2024-08-06 18:55 ` dpdklab
2024-08-06 18:57 ` dpdklab
2024-08-06 18:58 ` dpdklab
2024-08-06 18:59 ` dpdklab
2024-08-06 19:01 ` dpdklab
2024-08-06 19:03 ` dpdklab
2024-08-06 19:03 ` dpdklab
2024-08-06 19:05 ` dpdklab
2024-08-06 19:07 ` dpdklab
2024-08-06 19:08 ` dpdklab
2024-08-06 19:09 ` |SUCCESS| " dpdklab
2024-08-06 19:10 ` |PENDING| " dpdklab
2024-08-06 19:11 ` dpdklab
2024-08-06 19:11 ` dpdklab
2024-08-06 19:12 ` dpdklab [this message]
2024-08-06 19:13 ` |SUCCESS| " dpdklab
2024-08-06 19:21 ` dpdklab
2024-08-06 19:22 ` dpdklab
2024-08-06 19:23 ` dpdklab
2024-08-06 19:36 ` |PENDING| " dpdklab
2024-08-06 19:42 ` |SUCCESS| " dpdklab
2024-08-06 19:47 ` dpdklab
2024-08-06 19:52 ` dpdklab
2024-08-06 19:54 ` |PENDING| " dpdklab
2024-08-06 19:56 ` |SUCCESS| " dpdklab
2024-08-06 19:57 ` |PENDING| " dpdklab
2024-08-06 19:58 ` dpdklab
2024-08-06 20:01 ` dpdklab
2024-08-06 20:07 ` dpdklab
2024-08-06 20:10 ` dpdklab
2024-08-06 20:16 ` |SUCCESS| " dpdklab
2024-08-06 20:17 ` |PENDING| " dpdklab
2024-08-06 20:18 ` dpdklab
2024-08-06 20:20 ` dpdklab
2024-08-06 20:21 ` dpdklab
2024-08-06 20:24 ` dpdklab
2024-08-06 20:24 ` dpdklab
2024-08-06 20:26 ` dpdklab
2024-08-06 20:26 ` dpdklab
2024-08-06 20:27 ` dpdklab
2024-08-06 20:27 ` dpdklab
2024-08-06 20:30 ` dpdklab
2024-08-06 20:31 ` dpdklab
2024-08-06 20:31 ` dpdklab
2024-08-06 20:32 ` dpdklab
2024-08-06 20:33 ` dpdklab
2024-08-06 20:33 ` dpdklab
2024-08-06 20:34 ` dpdklab
2024-08-06 20:34 ` dpdklab
2024-08-06 20:35 ` dpdklab
2024-08-06 20:37 ` dpdklab
2024-08-06 20:37 ` dpdklab
2024-08-06 20:39 ` dpdklab
2024-08-06 20:39 ` dpdklab
2024-08-06 20:40 ` dpdklab
2024-08-06 20:40 ` dpdklab
2024-08-06 20:41 ` dpdklab
2024-08-06 20:43 ` dpdklab
2024-08-06 20:44 ` dpdklab
2024-08-06 20:46 ` dpdklab
2024-08-06 20:49 ` dpdklab
2024-08-06 20:51 ` dpdklab
2024-08-06 20:55 ` dpdklab
2024-08-06 20:58 ` |SUCCESS| " dpdklab
2024-08-06 21:02 ` |PENDING| " dpdklab
2024-08-06 21:04 ` dpdklab
2024-08-06 21:08 ` |SUCCESS| " dpdklab
2024-08-06 21:15 ` |PENDING| " dpdklab
2024-08-06 21:16 ` dpdklab
2024-08-06 21:17 ` dpdklab
2024-08-06 21:17 ` dpdklab
2024-08-06 21:18 ` dpdklab
2024-08-06 21:19 ` dpdklab
2024-08-06 21:20 ` dpdklab
2024-08-06 21:20 ` dpdklab
2024-08-06 21:20 ` dpdklab
2024-08-06 21:21 ` dpdklab
2024-08-06 21:22 ` dpdklab
2024-08-06 21:25 ` dpdklab
2024-08-06 21:27 ` dpdklab
2024-08-06 21:28 ` dpdklab
2024-08-06 21:31 ` dpdklab
2024-08-06 21:31 ` dpdklab
2024-08-06 21:34 ` dpdklab
2024-08-06 21:45 ` dpdklab
2024-08-06 21:46 ` dpdklab
2024-08-06 21:47 ` dpdklab
2024-08-06 21:50 ` |SUCCESS| " dpdklab
2024-08-06 22:03 ` dpdklab
2024-08-07  0:24 ` dpdklab
2024-08-07  7:11 ` dpdklab
2024-08-07  7:20 ` dpdklab
2024-08-07  7:32 ` 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=66b275ab.050a0220.118338.1d4eSMTPIN_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).