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| pw154259-154260 [PATCH] [2/2] test/lcore: fix build with M
Date: Tue, 10 Jun 2025 02:57:04 -0700 (PDT)	[thread overview]
Message-ID: <68480170.170a0220.312a8a.7850SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250610083643.8466-2-david.marchand@redhat.com>

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

_Functional Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, June 10 2025 08:36:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b1f3a7a8c375fbb66be48aed078222686d16fdb5

154259-154260 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#229903

Test environment and result as below:

Ubuntu 24.04 LTS
Kernel: 6.8.0-55-generic
Compiler: gcc 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/33371/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-06-10  9:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250610083643.8466-2-david.marchand@redhat.com>
2025-06-10  8:03 ` |SUCCESS| pw154259-154260 [PATCH 2/2] test/lcore: fix build with MSVC qemudev
2025-06-10  8:07 ` qemudev
2025-06-10  8:37 ` |SUCCESS| pw154260 " checkpatch
2025-06-10  9:45 ` 0-day Robot
2025-06-10  9:57 ` dpdklab [this message]
2025-06-10 10:00 ` |SUCCESS| pw154259-154260 [PATCH] [2/2] test/lcore: fix build with M dpdklab
2025-06-10 10:28 ` |PENDING| " dpdklab
2025-06-10 11:09 ` |SUCCESS| " dpdklab
2025-06-10 11:24 ` |PENDING| " dpdklab
2025-06-10 11:26 ` dpdklab
2025-06-10 11:29 ` |SUCCESS| " dpdklab
2025-06-10 11:35 ` |PENDING| " dpdklab
2025-06-10 12:27 ` |FAILURE| " dpdklab
2025-06-10 12:43 ` dpdklab
2025-06-10 13:46 ` |PENDING| " dpdklab
2025-06-10 14:04 ` |WARNING| " dpdklab
2025-06-10 20:27 ` |SUCCESS| " dpdklab
2025-06-10 20:28 ` dpdklab
2025-06-10 23:50 ` dpdklab
2025-06-10 23:50 ` dpdklab
2025-06-10 23:52 ` dpdklab
2025-06-10 23:52 ` dpdklab
2025-06-10 23:53 ` dpdklab
2025-06-10 23:53 ` dpdklab
2025-06-10 23:54 ` dpdklab
2025-06-11 14:01 ` 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=68480170.170a0220.312a8a.7850SMTPIN_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).