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| pw154599 [PATCH] net/virtio: Implement {rxq,txq}_info_get
Date: Thu, 19 Jun 2025 08:53:13 -0700 (PDT)	[thread overview]
Message-ID: <68543269.050a0220.30b76e.049bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250619115445.257679-1-hengqi.chen@gmail.com>

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

_Functional Testing PASS_

Submitter: Hengqi Chen <hengqi.chen@gmail.com>
Date: Thursday, June 19 2025 11:54:44 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:64267ffa9474c6becddcc07fc2e603adb621b44d

154599 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#231936

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

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-19 15:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250619115445.257679-1-hengqi.chen@gmail.com>
2025-06-19 11:48 ` |SUCCESS| pw154599 [PATCH] net/virtio: Implement {rxq, txq}_info_get callbacks qemudev
2025-06-19 11:53 ` qemudev
2025-06-19 11:55 ` checkpatch
2025-06-19 13:07 ` 0-day Robot
2025-06-19 14:52 ` |SUCCESS| pw154599 [PATCH] net/virtio: Implement {rxq,txq}_info_get dpdklab
2025-06-19 15:03 ` dpdklab
2025-06-19 15:07 ` dpdklab
2025-06-19 15:17 ` dpdklab
2025-06-19 15:53 ` dpdklab [this message]
2025-06-19 15:54 ` dpdklab
2025-06-19 16:21 ` dpdklab
2025-06-19 16:22 ` dpdklab
2025-06-19 16:41 ` |PENDING| " dpdklab
2025-06-19 16:51 ` dpdklab
2025-06-19 17:11 ` dpdklab
2025-06-19 17:22 ` |SUCCESS| " dpdklab
2025-06-19 18:24 ` dpdklab
2025-06-19 18:25 ` dpdklab
2025-06-19 18:41 ` dpdklab
2025-06-19 19:11 ` |WARNING| " dpdklab
2025-06-19 19:34 ` |FAILURE| " dpdklab
2025-06-19 20:02 ` dpdklab
2025-06-19 20:33 ` |SUCCESS| " dpdklab
2025-06-19 21:41 ` 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=68543269.050a0220.30b76e.049bSMTPIN_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).