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| pw157681 [PATCH] net/mlx5: fix spurious CPU wakeups caused
Date: Wed, 15 Oct 2025 07:57:34 -0700 (PDT)	[thread overview]
Message-ID: <68efb65e.6b0a0220.328823.0603SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251015133957.4094235-1-sivaprasad.tummala@amd.com>

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

_Functional Testing PASS_

Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Wednesday, October 15 2025 13:39:57 
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: master
  CommitID:2374f33e1d964e100895fd294966380c46f0886d

157681 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#249523

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps

Aggregate Results by Test Suite
+-----------------------------+--------+
|         Test Suite          | Result |
+=============================+========+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 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/34286/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-10-15 14:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251015133957.4094235-1-sivaprasad.tummala@amd.com>
2025-10-15 13:05 ` |SUCCESS| pw157681 [PATCH] net/mlx5: fix spurious CPU wakeups caused by invalid CQE qemudev
2025-10-15 13:10 ` qemudev
2025-10-15 13:41 ` checkpatch
2025-10-15 14:09 ` |PENDING| pw157681 [PATCH] net/mlx5: fix spurious CPU wakeups caused dpdklab
2025-10-15 14:13 ` |SUCCESS| " dpdklab
2025-10-15 14:17 ` dpdklab
2025-10-15 14:21 ` |PENDING| " dpdklab
2025-10-15 14:24 ` dpdklab
2025-10-15 14:24 ` dpdklab
2025-10-15 14:32 ` |SUCCESS| " dpdklab
2025-10-15 14:35 ` dpdklab
2025-10-15 14:35 ` dpdklab
2025-10-15 14:35 ` dpdklab
2025-10-15 14:49 ` dpdklab
2025-10-15 14:52 ` |PENDING| " dpdklab
2025-10-15 14:52 ` |SUCCESS| " dpdklab
2025-10-15 14:57 ` dpdklab [this message]
2025-10-15 15:14 ` |SUCCESS| pw157681 [PATCH] net/mlx5: fix spurious CPU wakeups caused by invalid CQE 0-day Robot
2025-10-15 15:14 ` 0-day Robot
2025-10-15 15:21 ` |SUCCESS| pw157681 [PATCH] net/mlx5: fix spurious CPU wakeups caused dpdklab
2025-10-15 15:29 ` dpdklab
2025-10-15 20:13 ` dpdklab
2025-10-15 20:13 ` dpdklab
2025-10-15 20:14 ` 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=68efb65e.6b0a0220.328823.0603SMTPIN_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).