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| pw144302-144316 [PATCH] [v25,15/15] doc: add release note
Date: Thu, 19 Sep 2024 12:39:39 -0700 (PDT)	[thread overview]
Message-ID: <66ec7dfb.630a0220.652f4.cfeaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240919150609.5281-16-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, September 19 2024 15:04:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144302-144316 --> testing pass

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

Test environment and result as below:

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


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

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

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

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

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-19 19:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240919150609.5281-16-stephen@networkplumber.org>
2024-09-19 14:42 ` |SUCCESS| pw144302-144316 [PATCH v25 15/15] doc: add release note about log library qemudev
2024-09-19 14:46 ` qemudev
2024-09-19 15:09 ` |SUCCESS| pw144316 " checkpatch
2024-09-19 16:04 ` 0-day Robot
2024-09-19 18:54 ` |SUCCESS| pw144302-144316 [PATCH] [v25,15/15] doc: add release note dpdklab
2024-09-19 18:56 ` dpdklab
2024-09-19 19:12 ` |FAILURE| " dpdklab
2024-09-19 19:39 ` dpdklab [this message]
2024-09-19 19:40 ` |SUCCESS| " dpdklab
2024-09-19 20:03 ` dpdklab
2024-09-19 20:05 ` |PENDING| " dpdklab
2024-09-19 20:11 ` |SUCCESS| " dpdklab
2024-09-19 20:19 ` dpdklab
2024-09-19 20:42 ` dpdklab
2024-09-19 22:01 ` dpdklab
2024-09-19 23:15 ` dpdklab
2024-09-19 23:49 ` |PENDING| " dpdklab
2024-09-20  0:27 ` |SUCCESS| " dpdklab
2024-09-20  2:30 ` dpdklab
2024-09-20  3:40 ` dpdklab
2024-09-21  4:39 ` dpdklab
2024-09-23  4:33 ` dpdklab
2024-09-23  4: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=66ec7dfb.630a0220.652f4.cfeaSMTPIN_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).