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| pw141959 [PATCH] dma/idxd: fix failure to configure a devi
Date: Fri, 28 Jun 2024 02:06:43 -0700 (PDT)	[thread overview]
Message-ID: <667e7d23.170a0220.ea012.4f24SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240628053458.78337-1-wenwux.ma@intel.com>

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

_Functional Testing PASS_

Submitter: Wenwu Ma <wenwux.ma@intel.com>
Date: Friday, June 28 2024 05:34:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b

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


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

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-28  9:09 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240628053458.78337-1-wenwux.ma@intel.com>
2024-06-28  5:24 ` |SUCCESS| pw141959 [PATCH] dma/idxd: fix failure to configure a device instance for DSA qemudev
2024-06-28  5:28 ` qemudev
2024-06-28  5:51 ` checkpatch
2024-06-28  6:28 ` |SUCCESS| pw141959 [PATCH] dma/idxd: fix failure to configure a devi dpdklab
2024-06-28  6:31 ` dpdklab
2024-06-28  6:32 ` dpdklab
2024-06-28  6:34 ` |PENDING| " dpdklab
2024-06-28  6:36 ` |SUCCESS| " dpdklab
2024-06-28  6:37 ` dpdklab
2024-06-28  6:45 ` dpdklab
2024-06-28  6:45 ` |SUCCESS| pw141959 [PATCH] dma/idxd: fix failure to configure a device instance for DSA 0-day Robot
2024-06-28  6:50 ` |SUCCESS| pw141959 [PATCH] dma/idxd: fix failure to configure a devi dpdklab
2024-06-28  6:50 ` dpdklab
2024-06-28  6:51 ` |PENDING| " dpdklab
2024-06-28  6:52 ` dpdklab
2024-06-28  6:52 ` dpdklab
2024-06-28  7:00 ` |SUCCESS| " dpdklab
2024-06-28  7:01 ` dpdklab
2024-06-28  7:02 ` |PENDING| " dpdklab
2024-06-28  7:07 ` dpdklab
2024-06-28  7:09 ` |SUCCESS| " dpdklab
2024-06-28  7:16 ` |PENDING| " dpdklab
2024-06-28  7:16 ` dpdklab
2024-06-28  7:19 ` dpdklab
2024-06-28  7:20 ` dpdklab
2024-06-28  7:21 ` dpdklab
2024-06-28  7:28 ` dpdklab
2024-06-28  7:30 ` dpdklab
2024-06-28  7:32 ` dpdklab
2024-06-28  7:36 ` dpdklab
2024-06-28  7:40 ` |SUCCESS| " dpdklab
2024-06-28  7:45 ` dpdklab
2024-06-28  8:09 ` dpdklab
2024-06-28  8:09 ` dpdklab
2024-06-28  8:13 ` dpdklab
2024-06-28  8:15 ` dpdklab
2024-06-28  8:20 ` dpdklab
2024-06-28  8:26 ` dpdklab
2024-06-28  8:28 ` dpdklab
2024-06-28  8:51 ` dpdklab
2024-06-28  8:57 ` dpdklab
2024-06-28  9:03 ` dpdklab
2024-06-28  9:06 ` dpdklab [this message]
2024-06-28  9:11 ` dpdklab
2024-06-28  9:31 ` dpdklab
2024-06-28 10:59 ` dpdklab
2024-06-28 11:03 ` dpdklab
2024-06-28 11:04 ` dpdklab
2024-06-28 11:04 ` dpdklab
2024-06-28 11:05 ` dpdklab
2024-06-28 11:13 ` dpdklab
2024-06-28 11:13 ` dpdklab
2024-06-28 11:18 ` dpdklab
2024-06-28 11:18 ` dpdklab
2024-06-28 11:23 ` dpdklab
2024-06-28 11:24 ` dpdklab
2024-06-28 11:26 ` dpdklab
2024-06-28 11:26 ` dpdklab
2024-06-28 11:28 ` dpdklab
2024-06-28 11:32 ` dpdklab
2024-06-28 11:33 ` dpdklab
2024-06-28 11:34 ` dpdklab
2024-06-28 12:58 ` dpdklab
2024-06-28 12:58 ` dpdklab
2024-06-28 13:09 ` dpdklab
2024-06-28 13:13 ` dpdklab
2024-06-28 13:18 ` dpdklab
2024-06-28 13:19 ` dpdklab
2024-06-28 13:20 ` dpdklab
2024-06-28 13:23 ` dpdklab
2024-06-28 13:25 ` dpdklab
2024-06-28 13:30 ` dpdklab
2024-06-28 13:30 ` dpdklab
2024-06-28 13:31 ` dpdklab
2024-06-28 13:31 ` dpdklab
2024-06-28 13:36 ` dpdklab
2024-06-28 13:46 ` dpdklab
2024-06-28 13:48 ` dpdklab
2024-06-28 13:54 ` dpdklab
2024-06-28 13:57 ` dpdklab
2024-06-28 13:57 ` dpdklab
2024-06-28 22:02 ` dpdklab
2024-06-28 22:16 ` dpdklab
2024-06-29  9:07 ` 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=667e7d23.170a0220.ea012.4f24SMTPIN_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).