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| pw141883-141890 [PATCH] [v3,8/8] net/mlx5: add async flow
Date: Wed, 26 Jun 2024 23:37:47 -0700 (PDT)	[thread overview]
Message-ID: <667d08bb.170a0220.90595.241eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240626181428.1678402-9-dsosnowski@nvidia.com>

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/141890

_Functional Testing PASS_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, June 26 2024 18:14:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f

141883-141890 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: Unknown

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


Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: Unknown

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


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: Unknown

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-27  6:37 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240626181428.1678402-9-dsosnowski@nvidia.com>
2024-06-26 17:49 ` |SUCCESS| pw141883-141890 [PATCH v3 8/8] net/mlx5: add async flow operation validation qemudev
2024-06-26 17:54 ` qemudev
2024-06-26 18:17 ` |SUCCESS| pw141890 " checkpatch
2024-06-26 19:05 ` 0-day Robot
2024-06-26 22:59 ` |SUCCESS| pw141883-141890 [PATCH] [v3,8/8] net/mlx5: add async flow dpdklab
2024-06-26 23:13 ` dpdklab
2024-06-26 23:26 ` dpdklab
2024-06-26 23:26 ` dpdklab
2024-06-26 23:31 ` dpdklab
2024-06-26 23:35 ` dpdklab
2024-06-26 23:44 ` dpdklab
2024-06-26 23:48 ` dpdklab
2024-06-27  0:40 ` dpdklab
2024-06-27  1:30 ` |PENDING| " dpdklab
2024-06-27  1:30 ` dpdklab
2024-06-27  1:37 ` dpdklab
2024-06-27  1:42 ` |SUCCESS| " dpdklab
2024-06-27  1:44 ` |PENDING| " dpdklab
2024-06-27  1:44 ` dpdklab
2024-06-27  1:46 ` dpdklab
2024-06-27  1:50 ` |SUCCESS| " dpdklab
2024-06-27  1:52 ` |PENDING| " dpdklab
2024-06-27  1:52 ` dpdklab
2024-06-27  1:53 ` dpdklab
2024-06-27  1:58 ` dpdklab
2024-06-27  2:00 ` dpdklab
2024-06-27  2:01 ` dpdklab
2024-06-27  2:04 ` dpdklab
2024-06-27  2:05 ` dpdklab
2024-06-27  2:12 ` |SUCCESS| " dpdklab
2024-06-27  2:15 ` dpdklab
2024-06-27  3:22 ` dpdklab
2024-06-27  3:24 ` dpdklab
2024-06-27  3:28 ` dpdklab
2024-06-27  3:28 ` dpdklab
2024-06-27  3:29 ` dpdklab
2024-06-27  4:02 ` dpdklab
2024-06-27  4:20 ` dpdklab
2024-06-27  5:38 ` dpdklab
2024-06-27  5:42 ` dpdklab
2024-06-27  6:11 ` dpdklab
2024-06-27  6:13 ` dpdklab
2024-06-27  6:23 ` dpdklab
2024-06-27  6:26 ` dpdklab
2024-06-27  6:28 ` dpdklab
2024-06-27  6:33 ` dpdklab
2024-06-27  6:34 ` dpdklab
2024-06-27  6:37 ` dpdklab [this message]
2024-06-27  6:47 ` dpdklab
2024-06-27  6:49 ` dpdklab
2024-06-27  6:50 ` dpdklab
2024-06-27  6:53 ` dpdklab
2024-06-27  6:56 ` dpdklab
2024-06-27  6:57 ` dpdklab
2024-06-27  6:59 ` dpdklab
2024-06-27  7:01 ` dpdklab
2024-06-27  7:04 ` dpdklab
2024-06-27  7:05 ` dpdklab
2024-06-27  7:06 ` dpdklab
2024-06-27  7:07 ` dpdklab
2024-06-27  7:07 ` dpdklab
2024-06-27  7:08 ` dpdklab
2024-06-27  7:10 ` dpdklab
2024-06-27  7:11 ` dpdklab
2024-06-27  7:14 ` dpdklab
2024-06-27  7:14 ` dpdklab
2024-06-27  7:14 ` dpdklab
2024-06-27  7:14 ` dpdklab
2024-06-27  7:14 ` dpdklab
2024-06-27  7:15 ` dpdklab
2024-06-27  7:15 ` dpdklab
2024-06-27  7:18 ` dpdklab
2024-06-27  7:19 ` dpdklab
2024-06-27  7:20 ` dpdklab
2024-06-27  7:20 ` dpdklab
2024-06-27  7:22 ` dpdklab
2024-06-27  7:25 ` dpdklab
2024-06-27  7:26 ` dpdklab
2024-06-27  7:27 ` dpdklab
2024-06-27  7:27 ` dpdklab
2024-06-27  7:28 ` dpdklab
2024-06-27  7:29 ` dpdklab
2024-06-27  7:34 ` dpdklab
2024-06-27  7:36 ` dpdklab
2024-06-27  7:42 ` dpdklab
2024-06-27  7:43 ` dpdklab
2024-06-27  7:44 ` dpdklab
2024-06-27  7:47 ` dpdklab
2024-06-27  7:49 ` dpdklab
2024-06-27  7:53 ` dpdklab
2024-06-27  7:54 ` dpdklab
2024-06-27  7:54 ` dpdklab
2024-06-27  7:54 ` dpdklab
2024-06-27  7:56 ` dpdklab
2024-06-27  7:59 ` dpdklab
2024-06-27  8:01 ` dpdklab
2024-06-27  8:01 ` dpdklab
2024-06-27  8:03 ` dpdklab
2024-06-27  8:07 ` dpdklab
2024-06-27  8:14 ` dpdklab
2024-06-27  8:21 ` dpdklab
2024-06-27  8:29 ` dpdklab
2024-06-27  8:30 ` dpdklab
2024-06-27  8:30 ` dpdklab
2024-06-27  8:31 ` dpdklab
2024-06-27  8:38 ` dpdklab
2024-06-27  8:40 ` dpdklab
2024-06-27 10:52 ` dpdklab
2024-06-28  1:32 ` dpdklab
2024-06-28  2:10 ` dpdklab
2024-06-29 12:48 ` 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=667d08bb.170a0220.90595.241eSMTPIN_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).