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| pw153798-153797 [PATCH] [v1,3/3] dts: fix doc generation b
Date: Tue, 03 Jun 2025 13:26:47 -0700 (PDT)	[thread overview]
Message-ID: <683f5a87.170a0220.241743.7523SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250527153734.368235-3-dmarx@iol.unh.edu>

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

_Functional Testing PASS_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Tuesday, May 27 2025 15:37:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1aef42bc97a31906486c9d66b792208948af06f3

153798-153797 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#227887

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
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/33257/

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-03 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250527153734.368235-3-dmarx@iol.unh.edu>
2025-05-27 15:37 ` |SUCCESS| pw153797 [PATCH v1 3/3] dts: fix doc generation bug checkpatch
2025-05-28  1:01 ` |SUCCESS| pw153798-153797 [PATCH] [v1,3/3] dts: fix doc generation b dpdklab
2025-05-28  1:16 ` dpdklab
2025-05-28  1:26 ` dpdklab
2025-05-28  1:42 ` dpdklab
2025-05-28  1:57 ` dpdklab
2025-05-28  2:35 ` dpdklab
2025-05-28  2:36 ` dpdklab
2025-06-03 20:26 ` dpdklab [this message]
2025-06-04  4:12 ` 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=683f5a87.170a0220.241743.7523SMTPIN_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).