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| pw144092 [PATCH] [v2] dts: fix runner target in the Docker
Date: Tue, 17 Sep 2024 00:23:24 -0700 (PDT)	[thread overview]
Message-ID: <66e92e6c.050a0220.f8f74.cc42SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240916181445.13997-1-jspewock@iol.unh.edu>

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

_Testing PASS_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Monday, September 16 2024 18:14:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144092 --> testing pass

Upstream job id: Windows-Compile-DPDK-VS#3117

Test environment and result as below:

+---------------------+-----------------------+----------------------+-------------------+--------------------+
|     Environment     | dpdk_win_llvm_compile | dpdk_mingw64_compile | dpdk_msvc_compile | dpdk_meson_compile |
+=====================+=======================+======================+===================+====================+
| Windows Server 2022 | PASS                  | PASS                 | PASS              | SKIPPED            |
+---------------------+-----------------------+----------------------+-------------------+--------------------+
| FreeBSD 13.3        | SKIPPED               | SKIPPED              | SKIPPED           | PASS               |
+---------------------+-----------------------+----------------------+-------------------+--------------------+
| FreeBSD 14.1        | SKIPPED               | 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/31040/

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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240916181445.13997-1-jspewock@iol.unh.edu>
2024-09-16 17:47 ` |SUCCESS| pw144092 [PATCH v2] dts: fix runner target in the Dockerfile qemudev
2024-09-16 17:52 ` qemudev
2024-09-16 18:16 ` checkpatch
2024-09-16 19:04 ` 0-day Robot
2024-09-17  6:44 ` |SUCCESS| pw144092 [PATCH] [v2] dts: fix runner target in the Docker dpdklab
2024-09-17  7:09 ` |PENDING| " dpdklab
2024-09-17  7:22 ` |SUCCESS| " dpdklab
2024-09-17  7:23 ` dpdklab [this message]
2024-09-17  7:34 ` |PENDING| " dpdklab
2024-09-17  8:19 ` |SUCCESS| " dpdklab
2024-09-17  8:24 ` dpdklab
2024-09-17  8:24 ` dpdklab
2024-09-17  8:51 ` dpdklab
2024-09-17  9:31 ` dpdklab
2024-09-17 11:09 ` dpdklab
2024-09-17 11:38 ` dpdklab
2024-09-17 11:41 ` dpdklab
2024-09-17 12:08 ` dpdklab
2024-09-17 12:11 ` dpdklab
2024-09-17 12:26 ` dpdklab
2024-09-17 21:12 ` dpdklab
2024-09-17 21:13 ` 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=66e92e6c.050a0220.f8f74.cc42SMTPIN_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).