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| pw154995 [PATCH] [v2] ci: check C++ headers with clang
Date: Fri, 04 Jul 2025 19:26:59 -0700 (PDT)	[thread overview]
Message-ID: <68688d73.050a0220.2d1800.7912SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250703082010.2002295-1-david.marchand@redhat.com>

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

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Thursday, July 03 2025 08:20:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70c2297528e7c7789af452f78de1932e9a20c8a2

154995 --> testing pass

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

Test environment and result as below:

+---------------------+-------------------+--------------------+-------------------------+----------------------+
|     Environment     | dpdk_msvc_compile | dpdk_meson_compile | dpdk_llvm_clang_compile | dpdk_mingw64_compile |
+=====================+===================+====================+=========================+======================+
| Windows Server 2022 | PASS              | SKIPPED            | PASS                    | PASS                 |
+---------------------+-------------------+--------------------+-------------------------+----------------------+
| Ubuntu 20.04        | SKIPPED           | PASS               | SKIPPED                 | SKIPPED              |
+---------------------+-------------------+--------------------+-------------------------+----------------------+


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

Ubuntu 20.04
	Kernel: 4.19
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-07-05  2:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250703082010.2002295-1-david.marchand@redhat.com>
2025-07-03  7:52 ` |SUCCESS| pw154995 [PATCH v2] " qemudev
2025-07-03  7:57 ` qemudev
2025-07-03  8:19 ` checkpatch
2025-07-03  9:43 ` 0-day Robot
2025-07-05  1:08 ` |SUCCESS| pw154995 [PATCH] [v2] " dpdklab
2025-07-05  1:10 ` |FAILURE| " dpdklab
2025-07-05  1:37 ` |PENDING| " dpdklab
2025-07-05  1:45 ` |SUCCESS| " dpdklab
2025-07-05  1:49 ` |PENDING| " dpdklab
2025-07-05  2:18 ` |SUCCESS| " dpdklab
2025-07-05  2:26 ` dpdklab [this message]
2025-07-05  3:18 ` |PENDING| " dpdklab
2025-07-05  3:38 ` |SUCCESS| " dpdklab
2025-07-05  4:13 ` |FAILURE| " dpdklab
2025-07-05  5:44 ` dpdklab
2025-07-05  6:14 ` dpdklab
2025-07-05  7:11 ` dpdklab
2025-07-05  9:22 ` |SUCCESS| " dpdklab
2025-07-05 10:09 ` dpdklab
2025-07-05 12:45 ` |WARNING| " dpdklab
2025-07-05 12:46 ` 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=68688d73.050a0220.2d1800.7912SMTPIN_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).