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| pw141882 [PATCH] net/ice: use a different method to filter
Date: Wed, 26 Jun 2024 16:30:12 -0700 (PDT)	[thread overview]
Message-ID: <667ca484.050a0220.75cc0.0465SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240626173155.2177002-1-vladimir.medvedkin@intel.com>

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

_Testing PASS_

Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Wednesday, June 26 2024 17:31:55 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c0fa83fe030771dea12e65ca1ba11174e1164774

141882 --> 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 | PASS               | 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/30326/

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-26 23:30 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240626173155.2177002-1-vladimir.medvedkin@intel.com>
2024-06-26 17:05 ` |SUCCESS| pw141882 [PATCH] net/ice: use a different method to filter LLDP packets qemudev
2024-06-26 17:09 ` qemudev
2024-06-26 17:32 ` checkpatch
2024-06-26 18:25 ` 0-day Robot
2024-06-26 19:02 ` |SUCCESS| pw141882 [PATCH] net/ice: use a different method to filter dpdklab
2024-06-26 19:11 ` dpdklab
2024-06-26 19:12 ` dpdklab
2024-06-26 19:24 ` dpdklab
2024-06-26 19:25 ` dpdklab
2024-06-26 19:35 ` dpdklab
2024-06-26 19:50 ` dpdklab
2024-06-26 20:11 ` dpdklab
2024-06-26 20:22 ` dpdklab
2024-06-26 20:24 ` dpdklab
2024-06-26 20:27 ` dpdklab
2024-06-26 20:29 ` dpdklab
2024-06-26 20:33 ` dpdklab
2024-06-26 20:34 ` dpdklab
2024-06-26 20:38 ` dpdklab
2024-06-26 20:52 ` |PENDING| " dpdklab
2024-06-26 20:54 ` dpdklab
2024-06-26 20:56 ` dpdklab
2024-06-26 20:58 ` dpdklab
2024-06-26 21:00 ` |SUCCESS| " dpdklab
2024-06-26 21:03 ` |PENDING| " dpdklab
2024-06-26 21:03 ` dpdklab
2024-06-26 21:05 ` dpdklab
2024-06-26 21:06 ` dpdklab
2024-06-26 21:07 ` dpdklab
2024-06-26 21:15 ` dpdklab
2024-06-26 21:16 ` dpdklab
2024-06-26 21:17 ` dpdklab
2024-06-26 21:18 ` dpdklab
2024-06-26 21:20 ` |SUCCESS| " dpdklab
2024-06-26 21:21 ` |PENDING| " dpdklab
2024-06-26 21:23 ` dpdklab
2024-06-26 21:32 ` |SUCCESS| " dpdklab
2024-06-26 22:55 ` dpdklab
2024-06-26 22:57 ` dpdklab
2024-06-26 23:00 ` dpdklab
2024-06-26 23:00 ` dpdklab
2024-06-26 23:02 ` dpdklab
2024-06-26 23:08 ` dpdklab
2024-06-26 23:26 ` dpdklab
2024-06-26 23:30 ` dpdklab [this message]
2024-06-27  0:42 ` dpdklab
2024-06-27  0:46 ` dpdklab
2024-06-27  0:50 ` dpdklab
2024-06-27  0:50 ` dpdklab
2024-06-27  0:51 ` dpdklab
2024-06-27  0:51 ` dpdklab
2024-06-27  0:56 ` dpdklab
2024-06-27  1:03 ` dpdklab
2024-06-27  1:05 ` dpdklab
2024-06-27  1:09 ` dpdklab
2024-06-27  1:09 ` dpdklab
2024-06-27  1:11 ` dpdklab
2024-06-27  1:12 ` dpdklab
2024-06-27  1:13 ` dpdklab
2024-06-27  1:13 ` dpdklab
2024-06-27  1:14 ` dpdklab
2024-06-27  1:17 ` dpdklab
2024-06-27  1:17 ` dpdklab
2024-06-27  1:18 ` dpdklab
2024-06-27  1:18 ` dpdklab
2024-06-27  1:20 ` dpdklab
2024-06-27  1:24 ` dpdklab
2024-06-27  1:25 ` dpdklab
2024-06-27  1:26 ` dpdklab
2024-06-27  1:27 ` dpdklab
2024-06-27  1:27 ` dpdklab
2024-06-27  1:29 ` dpdklab
2024-06-27  1:30 ` dpdklab
2024-06-27  1:39 ` dpdklab
2024-06-27  1:43 ` dpdklab
2024-06-27  1:48 ` dpdklab
2024-06-27  1:55 ` dpdklab
2024-06-27  1:55 ` dpdklab
2024-06-27  1:59 ` dpdklab
2024-06-27  2:03 ` dpdklab
2024-06-27  2:03 ` dpdklab
2024-06-27  2:09 ` dpdklab
2024-06-27  2:10 ` dpdklab
2024-06-27  2:11 ` dpdklab
2024-06-27  2:20 ` dpdklab
2024-06-27  2:26 ` dpdklab
2024-06-27  2:27 ` dpdklab
2024-06-27  2:32 ` dpdklab
2024-06-27  2:34 ` dpdklab
2024-06-27  2:35 ` dpdklab
2024-06-27  2:38 ` dpdklab
2024-06-27  2:39 ` dpdklab
2024-06-27  2:44 ` dpdklab
2024-06-27  2:44 ` dpdklab
2024-06-27  2:45 ` dpdklab
2024-06-27  2:47 ` dpdklab
2024-06-27  2:49 ` dpdklab
2024-06-27  2:50 ` dpdklab
2024-06-27  2:56 ` dpdklab
2024-06-27  2:59 ` dpdklab
2024-06-27  2:59 ` dpdklab
2024-06-27  3:02 ` dpdklab
2024-06-27  3:02 ` dpdklab
2024-06-27  3:03 ` dpdklab
2024-06-27  3:04 ` dpdklab
2024-06-27  3:05 ` dpdklab
2024-06-27  3:09 ` dpdklab
2024-06-27  3:11 ` dpdklab
2024-06-27  3:14 ` dpdklab
2024-06-27  3:14 ` dpdklab
2024-06-27  3:15 ` dpdklab
2024-06-27  3:25 ` dpdklab
2024-06-27  3:52 ` dpdklab
2024-06-27 11:41 ` dpdklab
2024-06-27 12:14 ` dpdklab
2024-06-28  5:02 ` 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=667ca484.050a0220.75cc0.0465SMTPIN_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).