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| pw154180-154181 [PATCH] [v1,2/2] net/e1000: update README
Date: Mon, 09 Jun 2025 12:47:41 -0700 (PDT)	[thread overview]
Message-ID: <68473a5d.170a0220.36d296.32aeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <9a5149bae160064c943ac8e9d8e557e9e1c5e3f1.1749464159.git.anatoly.burakov@intel.com>

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

_Functional Testing PASS_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Monday, June 09 2025 10:16:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8ec1f7a6d1ba204344127e2780ea4a19146d647d

154180-154181 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#229738

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  |
+----------------------------+--------+


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/33358/

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-09 19:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9a5149bae160064c943ac8e9d8e557e9e1c5e3f1.1749464159.git.anatoly.burakov@intel.com>
2025-06-09  9:47 ` |SUCCESS| pw154180-154181 [PATCH v1 2/2] " qemudev
2025-06-09  9:53 ` |FAILURE| " qemudev
2025-06-09 10:16 ` |SUCCESS| pw154181 " checkpatch
2025-06-09 11:25 ` 0-day Robot
2025-06-09 17:13 ` |SUCCESS| pw154180-154181 [PATCH] [v1,2/2] " dpdklab
2025-06-09 17:17 ` |PENDING| " dpdklab
2025-06-09 17:22 ` dpdklab
2025-06-09 17:24 ` |SUCCESS| " dpdklab
2025-06-09 17:42 ` |WARNING| " dpdklab
2025-06-09 17:57 ` |PENDING| " dpdklab
2025-06-09 18:03 ` dpdklab
2025-06-09 18:40 ` dpdklab
2025-06-09 18:54 ` |WARNING| " dpdklab
2025-06-09 18:59 ` |SUCCESS| " dpdklab
2025-06-09 19:16 ` dpdklab
2025-06-09 19:24 ` |PENDING| " dpdklab
2025-06-09 19:47 ` dpdklab [this message]
2025-06-09 20:27 ` dpdklab
2025-06-09 20:29 ` |SUCCESS| " dpdklab
2025-06-09 20:42 ` dpdklab
2025-06-09 23:12 ` |WARNING| " dpdklab
2025-06-09 23:16 ` |PENDING| " dpdklab
2025-06-10  0:27 ` |WARNING| " dpdklab
2025-06-10  0:28 ` dpdklab
2025-06-10  0:31 ` dpdklab
2025-06-10  0:31 ` dpdklab
2025-06-10  0:33 ` dpdklab
2025-06-10  1:20 ` |SUCCESS| " dpdklab
2025-06-10  2:20 ` dpdklab
2025-06-10  2:42 ` dpdklab
2025-06-10  2:43 ` 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=68473a5d.170a0220.36d296.32aeSMTPIN_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).