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| pw155606-155608 [PATCH] [v2,3/3] ethdev: Reject conflictin
Date: Thu, 31 Jul 2025 06:49:20 -0700 (PDT)	[thread overview]
Message-ID: <688b7460.050a0220.1e0878.37b9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250731125603.672860-3-mb@smartsharesystems.com>

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

_Functional Testing PASS_

Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Thursday, July 31 2025 12:56:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fc8df05a80b681f3dd2fc45283462b3a97a955ee

155606-155608 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#238757

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps

Aggregate Results by Test Suite
+----------------------------+--------+
|         Test Suite         | Result |
+============================+========+
| crypto_perf_cryptodev_perf |  PASS  |
+----------------------------+--------+


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


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33789/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-07-31 13:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250731125603.672860-3-mb@smartsharesystems.com>
2025-07-31 12:29 ` |SUCCESS| pw155606-155608 [PATCH v2 3/3] ethdev: Reject conflicting TX offloads configuration qemudev
2025-07-31 12:34 ` qemudev
2025-07-31 12:56 ` |SUCCESS| pw155608 " checkpatch
2025-07-31 13:32 ` |SUCCESS| pw155606-155608 [PATCH] [v2,3/3] ethdev: Reject conflictin dpdklab
2025-07-31 13:36 ` dpdklab
2025-07-31 13:41 ` dpdklab
2025-07-31 13:42 ` |PENDING| " dpdklab
2025-07-31 13:48 ` |FAILURE| " dpdklab
2025-07-31 13:49 ` dpdklab
2025-07-31 13:49 ` dpdklab [this message]
2025-07-31 14:00 ` |SUCCESS| " dpdklab
2025-07-31 14:04 ` dpdklab
2025-07-31 14:04 ` dpdklab
2025-07-31 14:10 ` dpdklab
2025-07-31 14:19 ` dpdklab
2025-07-31 14:25 ` |SUCCESS| pw155608 [PATCH v2 3/3] ethdev: Reject conflicting TX offloads configuration 0-day Robot
2025-07-31 14:36 ` |SUCCESS| pw155606-155608 [PATCH] [v2,3/3] ethdev: Reject conflictin dpdklab
2025-07-31 16:49 ` dpdklab
2025-08-01  0:36 ` |SUCCESS| pw155606-155608 [PATCH v2 3/3] ethdev: Reject conflicting TX offloads configuration qemudev
2025-08-01  0:40 ` qemudev

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=688b7460.050a0220.1e0878.37b9SMTPIN_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).