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| pw154903 [PATCH] ci: check C++ headers with clang
Date: Tue, 01 Jul 2025 09:43:00 -0700 (PDT)	[thread overview]
Message-ID: <68641014.050a0220.192ef3.ecbeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250701113146.1268492-1-david.marchand@redhat.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/154903

_Functional Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, July 01 2025 11:31:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:20460dcffd08a4680f881c39916ae783ee830374

154903 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#234378

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Intel Corporation QAT 8970 0 Mbps

Aggregate Results by Test Suite
+----------------------------+--------+
|         Test Suite         | Result |
+============================+========+
| crypto_perf_cryptodev_perf |  PASS  |
+----------------------------+--------+


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

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-01 16:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250701113146.1268492-1-david.marchand@redhat.com>
2025-07-01 10:59 ` qemudev
2025-07-01 11:03 ` qemudev
2025-07-01 11:32 ` checkpatch
2025-07-01 12:43 ` 0-day Robot
2025-07-01 16:18 ` dpdklab
2025-07-01 16:19 ` dpdklab
2025-07-01 16:31 ` dpdklab
2025-07-01 16:43 ` dpdklab [this message]
2025-07-01 16:44 ` dpdklab
2025-07-01 16:59 ` dpdklab
2025-07-01 18:00 ` |PENDING| " dpdklab
2025-07-01 18:18 ` |SUCCESS| " dpdklab
2025-07-01 18:35 ` |PENDING| " dpdklab
2025-07-01 18:58 ` |SUCCESS| " dpdklab
2025-07-01 19:40 ` |PENDING| " dpdklab
2025-07-01 19:51 ` |SUCCESS| " dpdklab
2025-07-01 19:53 ` dpdklab
2025-07-01 20:23 ` dpdklab
2025-07-01 20:35 ` |PENDING| " dpdklab
2025-07-01 21:30 ` dpdklab
2025-07-01 22:35 ` |SUCCESS| " dpdklab
2025-07-01 22:39 ` dpdklab
2025-07-02  0:11 ` |WARNING| " dpdklab
2025-07-02  1:49 ` |SUCCESS| " dpdklab
2025-07-02  1:49 ` dpdklab
2025-07-02  3:24 ` 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=68641014.050a0220.192ef3.ecbeSMTPIN_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).