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| pw141347 [PATCH] net/nfp: fix flow mask table entry proble
Date: Thu, 20 Jun 2024 05:21:52 -0700 (PDT)	[thread overview]
Message-ID: <66741ee0.170a0220.32afa.add4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240619095336.3479640-1-chaoyong.he@corigine.com>

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

_Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Wednesday, June 19 2024 09:53:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fbba6db3640f9f623c29c452e1a6b057073e81d2

141347 --> testing pass

Test environment and result as below:

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


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

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

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

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-20 12:21 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240619095336.3479640-1-chaoyong.he@corigine.com>
2024-06-19  9:32 ` |SUCCESS| pw141347 [PATCH] net/nfp: fix flow mask table entry problem qemudev
2024-06-19  9:36 ` qemudev
2024-06-19  9:54 ` checkpatch
2024-06-19 10:46 ` 0-day Robot
2024-06-20 10:53 ` |SUCCESS| pw141347 [PATCH] net/nfp: fix flow mask table entry proble dpdklab
2024-06-20 10:54 ` dpdklab
2024-06-20 10:59 ` dpdklab
2024-06-20 11:00 ` dpdklab
2024-06-20 11:11 ` dpdklab
2024-06-20 11:16 ` dpdklab
2024-06-20 11:16 ` dpdklab
2024-06-20 11:17 ` dpdklab
2024-06-20 11:17 ` dpdklab
2024-06-20 11:17 ` dpdklab
2024-06-20 11:18 ` dpdklab
2024-06-20 11:50 ` dpdklab
2024-06-20 11:59 ` dpdklab
2024-06-20 12:00 ` dpdklab
2024-06-20 12:04 ` dpdklab
2024-06-20 12:05 ` dpdklab
2024-06-20 12:06 ` dpdklab
2024-06-20 12:07 ` dpdklab
2024-06-20 12:08 ` dpdklab
2024-06-20 12:09 ` dpdklab
2024-06-20 12:10 ` dpdklab
2024-06-20 12:14 ` dpdklab
2024-06-20 12:15 ` dpdklab
2024-06-20 12:17 ` dpdklab
2024-06-20 12:18 ` dpdklab
2024-06-20 12:19 ` dpdklab
2024-06-20 12:20 ` dpdklab
2024-06-20 12:21 ` dpdklab [this message]
2024-06-20 12:22 ` dpdklab
2024-06-20 12:23 ` dpdklab
2024-06-20 12:23 ` dpdklab
2024-06-20 12:24 ` dpdklab
2024-06-20 12:28 ` dpdklab
2024-06-20 12:39 ` dpdklab
2024-06-20 12:47 ` dpdklab
2024-06-20 12:49 ` dpdklab
2024-06-20 12:52 ` dpdklab
2024-06-20 14:13 ` dpdklab
2024-06-20 14:13 ` dpdklab
2024-06-20 14:15 ` dpdklab
2024-06-20 14:20 ` dpdklab
2024-06-20 14:22 ` dpdklab
2024-06-20 14:29 ` dpdklab
2024-06-20 14:30 ` dpdklab
2024-06-20 14:31 ` dpdklab
2024-06-20 14:36 ` dpdklab
2024-06-20 14:38 ` dpdklab
2024-06-20 14:42 ` dpdklab
2024-06-20 14:43 ` dpdklab
2024-06-20 14:44 ` dpdklab
2024-06-20 14:45 ` dpdklab
2024-06-20 14:46 ` dpdklab
2024-06-20 14:47 ` dpdklab
2024-06-20 14:47 ` dpdklab
2024-06-20 14:57 ` dpdklab
2024-06-20 14:59 ` dpdklab
2024-06-20 14:59 ` dpdklab
2024-06-20 15:00 ` dpdklab
2024-06-20 15:01 ` dpdklab
2024-06-20 15:04 ` dpdklab
2024-06-20 15:05 ` dpdklab
2024-06-20 15:06 ` dpdklab
2024-06-20 15:07 ` dpdklab
2024-06-20 15:09 ` dpdklab
2024-06-20 15:10 ` dpdklab
2024-06-20 15:12 ` dpdklab
2024-06-20 15:12 ` dpdklab
2024-06-20 15:14 ` dpdklab
2024-06-20 15:15 ` dpdklab
2024-06-20 15:17 ` dpdklab
2024-06-20 15:18 ` dpdklab
2024-06-20 15:19 ` dpdklab
2024-06-20 15:19 ` dpdklab
2024-06-20 15:19 ` dpdklab
2024-06-20 15:20 ` dpdklab
2024-06-20 15:20 ` dpdklab
2024-06-20 15:23 ` dpdklab
2024-06-20 15:28 ` dpdklab
2024-06-20 15:28 ` dpdklab
2024-06-20 15:28 ` dpdklab
2024-06-20 15:30 ` dpdklab
2024-06-20 15:30 ` dpdklab
2024-06-20 15:30 ` dpdklab
2024-06-20 15:31 ` dpdklab
2024-06-20 15:31 ` dpdklab
2024-06-20 15:31 ` dpdklab
2024-06-20 15:33 ` dpdklab
2024-06-20 15:37 ` dpdklab
2024-06-20 15:40 ` dpdklab
2024-06-20 15:40 ` dpdklab
2024-06-20 15:41 ` dpdklab
2024-06-20 15:42 ` dpdklab
2024-06-20 15:44 ` dpdklab
2024-06-20 15:44 ` dpdklab
2024-06-20 15:46 ` dpdklab
2024-06-20 15:50 ` dpdklab
2024-06-20 15:50 ` dpdklab
2024-06-20 15:51 ` dpdklab
2024-06-20 15:51 ` dpdklab
2024-06-20 15:59 ` dpdklab
2024-06-20 16:02 ` dpdklab
2024-06-20 16:09 ` dpdklab
2024-06-20 16:14 ` dpdklab
2024-06-20 16:21 ` dpdklab
2024-06-20 16:25 ` dpdklab
2024-06-20 16:36 ` dpdklab
2024-06-20 17:11 ` dpdklab
2024-06-20 18:27 ` dpdklab
2024-06-20 23:56 ` dpdklab
2024-06-21  0:49 ` dpdklab
2024-06-22  3:12 ` 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=66741ee0.170a0220.32afa.add4SMTPIN_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).