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| pw142520 [PATCH] eal: fix device unregister for event regi
Date: Fri, 19 Jul 2024 02:00:31 -0700 (PDT)	[thread overview]
Message-ID: <669a2b2f.050a0220.a3284.4d23SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1721331448-9225-1-git-send-email-longli@linuxonhyperv.com>

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

_Functional Testing PASS_

Submitter: Long Li <longli@linuxonhyperv.com>
Date: Thursday, July 18 2024 19:37:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142520 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#168994

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

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

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

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-19  9:15 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1721331448-9225-1-git-send-email-longli@linuxonhyperv.com>
2024-07-18 19:12 ` |SUCCESS| pw142520 [PATCH] eal: fix device unregister for event registered with device_name NULL qemudev
2024-07-18 19:17 ` qemudev
2024-07-18 19:38 ` |WARNING| " checkpatch
2024-07-18 20:23 ` |SUCCESS| " 0-day Robot
2024-07-19  6:17 ` |SUCCESS| pw142520 [PATCH] eal: fix device unregister for event regi dpdklab
2024-07-19  6:20 ` dpdklab
2024-07-19  6:25 ` dpdklab
2024-07-19  6:33 ` dpdklab
2024-07-19  6:34 ` dpdklab
2024-07-19  6:39 ` dpdklab
2024-07-19  6:47 ` dpdklab
2024-07-19  7:03 ` |PENDING| " dpdklab
2024-07-19  7:05 ` dpdklab
2024-07-19  7:08 ` dpdklab
2024-07-19  7:12 ` |SUCCESS| " dpdklab
2024-07-19  7:13 ` |PENDING| " dpdklab
2024-07-19  7:14 ` dpdklab
2024-07-19  7:15 ` dpdklab
2024-07-19  7:20 ` dpdklab
2024-07-19  7:23 ` dpdklab
2024-07-19  7:23 ` dpdklab
2024-07-19  7:28 ` dpdklab
2024-07-19  7:29 ` dpdklab
2024-07-19  7:31 ` dpdklab
2024-07-19  7:31 ` dpdklab
2024-07-19  7:34 ` |SUCCESS| " dpdklab
2024-07-19  7:34 ` |PENDING| " dpdklab
2024-07-19  7:36 ` |SUCCESS| " dpdklab
2024-07-19  7:36 ` |PENDING| " dpdklab
2024-07-19  7:37 ` |SUCCESS| " dpdklab
2024-07-19  7:38 ` |PENDING| " dpdklab
2024-07-19  7:39 ` dpdklab
2024-07-19  7:41 ` dpdklab
2024-07-19  7:44 ` dpdklab
2024-07-19  7:45 ` dpdklab
2024-07-19  7:46 ` dpdklab
2024-07-19  7:46 ` dpdklab
2024-07-19  7:48 ` dpdklab
2024-07-19  7:50 ` dpdklab
2024-07-19  7:52 ` dpdklab
2024-07-19  7:59 ` dpdklab
2024-07-19  8:01 ` |SUCCESS| " dpdklab
2024-07-19  8:04 ` |PENDING| " dpdklab
2024-07-19  8:05 ` dpdklab
2024-07-19  8:08 ` dpdklab
2024-07-19  8:15 ` dpdklab
2024-07-19  8:19 ` dpdklab
2024-07-19  8:19 ` dpdklab
2024-07-19  8:25 ` dpdklab
2024-07-19  8:26 ` dpdklab
2024-07-19  8:28 ` dpdklab
2024-07-19  8:30 ` dpdklab
2024-07-19  8:33 ` dpdklab
2024-07-19  8:34 ` dpdklab
2024-07-19  8:34 ` dpdklab
2024-07-19  8:36 ` dpdklab
2024-07-19  8:36 ` |SUCCESS| " dpdklab
2024-07-19  8:37 ` |PENDING| " dpdklab
2024-07-19  8:38 ` dpdklab
2024-07-19  8:39 ` dpdklab
2024-07-19  8:41 ` dpdklab
2024-07-19  8:41 ` dpdklab
2024-07-19  8:44 ` dpdklab
2024-07-19  8:44 ` dpdklab
2024-07-19  8:46 ` dpdklab
2024-07-19  8:47 ` dpdklab
2024-07-19  8:55 ` |SUCCESS| " dpdklab
2024-07-19  8:57 ` |PENDING| " dpdklab
2024-07-19  9:00 ` dpdklab [this message]
2024-07-19  9:00 ` |SUCCESS| " dpdklab
2024-07-19  9:02 ` |PENDING| " dpdklab
2024-07-19  9:02 ` dpdklab
2024-07-19  9:04 ` dpdklab
2024-07-19  9:05 ` |SUCCESS| " dpdklab
2024-07-19  9:06 ` |PENDING| " dpdklab
2024-07-19  9:08 ` dpdklab
2024-07-19  9:12 ` |SUCCESS| " dpdklab
2024-07-19  9:14 ` |PENDING| " dpdklab
2024-07-19  9:21 ` dpdklab
2024-07-19  9:21 ` dpdklab
2024-07-19  9:25 ` dpdklab
2024-07-19  9:32 ` dpdklab
2024-07-19  9:33 ` |SUCCESS| " dpdklab
2024-07-19  9:33 ` |PENDING| " dpdklab
2024-07-19  9:35 ` dpdklab
2024-07-19  9:38 ` dpdklab
2024-07-19  9:43 ` |SUCCESS| " dpdklab
2024-07-19  9:43 ` |PENDING| " dpdklab
2024-07-19  9:46 ` dpdklab
2024-07-19  9:51 ` |SUCCESS| " dpdklab
2024-07-19  9:53 ` dpdklab
2024-07-19  9:56 ` |PENDING| " dpdklab
2024-07-19  9:57 ` dpdklab
2024-07-19  9:59 ` dpdklab
2024-07-19 10:01 ` dpdklab
2024-07-19 10:02 ` dpdklab
2024-07-19 10:04 ` dpdklab
2024-07-19 10:07 ` dpdklab
2024-07-19 10:09 ` dpdklab
2024-07-19 10:11 ` dpdklab
2024-07-19 10:13 ` |SUCCESS| " dpdklab
2024-07-19 10:14 ` dpdklab
2024-07-19 10:15 ` |PENDING| " dpdklab
2024-07-19 10:16 ` dpdklab
2024-07-19 10:17 ` dpdklab
2024-07-19 10:18 ` dpdklab
2024-07-19 10:21 ` dpdklab
2024-07-19 10:22 ` dpdklab
2024-07-19 10:24 ` dpdklab
2024-07-19 10:29 ` dpdklab
2024-07-19 10:30 ` dpdklab
2024-07-19 10:32 ` dpdklab
2024-07-19 10:33 ` dpdklab
2024-07-19 10:36 ` dpdklab
2024-07-19 11:00 ` |SUCCESS| " dpdklab
2024-07-19 12:33 ` 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=669a2b2f.050a0220.a3284.4d23SMTPIN_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).