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| pw144687 [PATCH] [v2] net/ice/base: update README
Date: Mon, 30 Sep 2024 12:46:30 -0700 (PDT)	[thread overview]
Message-ID: <66fb0016.170a0220.34396.2d04SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240930122211.16315-1-ian.stokes@intel.com>

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

_Testing PASS_

Submitter: Stokes, Ian <ian.stokes@intel.com>
Date: Monday, September 30 2024 12:22:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b8cdc85305107dfeb54dd35ad2c00b0632c71044

144687 --> testing pass

Upstream job id: Windows-Compile-DPDK-Native#22602

Test environment and result as below:

+---------------------+--------------------+-----------------------+-------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_win_llvm_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+====================+=======================+===================+======================+
| FreeBSD 13.4        | PASS               | SKIPPED               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-----------------------+-------------------+----------------------+
| FreeBSD 14.1        | PASS               | SKIPPED               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-----------------------+-------------------+----------------------+
| Windows Server 2022 | SKIPPED            | PASS                  | PASS              | PASS                 |
+---------------------+--------------------+-----------------------+-------------------+----------------------+


FreeBSD 13.4
	Kernel: 13.4-RELEASE-p1
	Compiler: clang 18.1.6

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31184/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-30 19:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240930122211.16315-1-ian.stokes@intel.com>
2024-09-30 12:07 ` |SUCCESS| pw144687 [PATCH v2] " qemudev
2024-09-30 12:12 ` qemudev
2024-09-30 12:23 ` |WARNING| " checkpatch
2024-09-30 19:15 ` |SUCCESS| pw144687 [PATCH] [v2] " dpdklab
2024-09-30 19:16 ` dpdklab
2024-09-30 19:23 ` dpdklab
2024-09-30 19:26 ` dpdklab
2024-09-30 19:28 ` dpdklab
2024-09-30 19:30 ` |PENDING| " dpdklab
2024-09-30 19:30 ` |SUCCESS| " dpdklab
2024-09-30 19:46 ` dpdklab [this message]
2024-09-30 19:53 ` |PENDING| " dpdklab
2024-09-30 19:54 ` |SUCCESS| " dpdklab
2024-09-30 19:54 ` |PENDING| " dpdklab
2024-09-30 20:15 ` |SUCCESS| " dpdklab
2024-09-30 20:42 ` |PENDING| " dpdklab
2024-09-30 20:46 ` |SUCCESS| " dpdklab
2024-09-30 21:04 ` dpdklab
2024-09-30 21:12 ` dpdklab
2024-09-30 22:22 ` dpdklab
2024-09-30 22:45 ` 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=66fb0016.170a0220.34396.2d04SMTPIN_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).