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| pw155687 [PATCH] [v5] eal: fix uncheck lcore role
Date: Wed, 06 Aug 2025 20:30:29 -0700 (PDT)	[thread overview]
Message-ID: <68941dd5.050a0220.32240.bc99SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250807024936.2039379-1-huangdengdui@huawei.com>

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

_Functional Testing PASS_

Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Thursday, August 07 2025 02:49:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:38543d33bd47fc0ee21f59db80a8763620741879

155687 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#239414

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 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/33826/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-08-07  3:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250807024936.2039379-1-huangdengdui@huawei.com>
2025-08-07  2:15 ` |SUCCESS| pw155687 [PATCH v5] " qemudev
2025-08-07  2:20 ` qemudev
2025-08-07  2:48 ` checkpatch
2025-08-07  3:24 ` |SUCCESS| pw155687 [PATCH] [v5] " dpdklab
2025-08-07  3:27 ` |PENDING| " dpdklab
2025-08-07  3:30 ` dpdklab [this message]
2025-08-07  3:38 ` |SUCCESS| " dpdklab
2025-08-07  3:41 ` |PENDING| " dpdklab
2025-08-07  3:41 ` |SUCCESS| " dpdklab
2025-08-07  3:42 ` dpdklab
2025-08-07  4:03 ` dpdklab
2025-08-07  4:16 ` dpdklab
2025-08-07  4:29 ` dpdklab
2025-08-07  4:33 ` dpdklab
2025-08-07  4:34 ` dpdklab
2025-08-07  8:06 ` dpdklab
2025-08-07  9:23 ` |SUCCESS| pw155687 [PATCH v5] " 0-day Robot
2025-08-07 10:26 ` |SUCCESS| pw155687 [PATCH] [v5] " dpdklab
2025-08-07 10:28 ` dpdklab
2025-08-07 10:29 ` dpdklab
2025-08-07 10:35 ` dpdklab
2025-08-07 10:35 ` dpdklab
2025-08-07 10:37 ` dpdklab
2025-08-07 10:41 ` dpdklab
2025-08-07 10:42 ` dpdklab
2025-08-07 10:42 ` dpdklab
2025-08-07 15:35 ` 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=68941dd5.050a0220.32240.bc99SMTPIN_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).