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| pw142332-142334 [PATCH] [v6,3/3] event/dlb2: enhance DLB c
Date: Sat, 13 Jul 2024 22:49:13 -0700 (PDT)	[thread overview]
Message-ID: <669366d9.050a0220.b1e25.b76dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240712001723.2791461-4-abdullah.sevincer@intel.com>

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

_Functional Testing PASS_

Submitter: Abdullah Sevincer <abdullah.sevincer@intel.com>
Date: Friday, July 12 2024 00:17:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:55b2c404060c59fa769d5127a19b947e8de79cac

142332-142334 --> functional testing pass

Test environment and result as below:

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


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


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

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-14  5:56 UTC|newest]

Thread overview: 119+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240712001723.2791461-4-abdullah.sevincer@intel.com>
2024-07-11 23:57 ` |SUCCESS| pw142332-142334 [PATCH v6 3/3] event/dlb2: enhance DLB credit handling qemudev
2024-07-12  0:01 ` qemudev
2024-07-12  0:19 ` |SUCCESS| pw142334 " checkpatch
2024-07-12  1:03 ` 0-day Robot
2024-07-12  1:40 ` |SUCCESS| pw142332-142334 [PATCH] [v6,3/3] event/dlb2: enhance DLB c dpdklab
2024-07-12  1:44 ` dpdklab
2024-07-12  1:44 ` dpdklab
2024-07-12  1:46 ` dpdklab
2024-07-12  1:48 ` dpdklab
2024-07-12  1:49 ` |PENDING| " dpdklab
2024-07-12  1:49 ` |SUCCESS| " dpdklab
2024-07-12  1:50 ` dpdklab
2024-07-12  1:51 ` |PENDING| " dpdklab
2024-07-12  1:51 ` dpdklab
2024-07-12  1:52 ` |SUCCESS| " dpdklab
2024-07-12  1:53 ` |PENDING| " dpdklab
2024-07-12  1:53 ` dpdklab
2024-07-12  1:54 ` dpdklab
2024-07-12  1:58 ` dpdklab
2024-07-12  1:59 ` dpdklab
2024-07-12  2:00 ` |SUCCESS| " dpdklab
2024-07-12  2:01 ` dpdklab
2024-07-12  2:02 ` |PENDING| " dpdklab
2024-07-12  2:05 ` |SUCCESS| " dpdklab
2024-07-12  2:05 ` dpdklab
2024-07-12  2:05 ` dpdklab
2024-07-12  2:07 ` dpdklab
2024-07-12  2:10 ` |PENDING| " dpdklab
2024-07-12  2:10 ` dpdklab
2024-07-12  2:12 ` dpdklab
2024-07-12  2:15 ` dpdklab
2024-07-12  2:15 ` dpdklab
2024-07-12  2:16 ` dpdklab
2024-07-12  2:19 ` |SUCCESS| " dpdklab
2024-07-12  2:23 ` |PENDING| " dpdklab
2024-07-12  2:27 ` |SUCCESS| " dpdklab
2024-07-12  2:30 ` |PENDING| " dpdklab
2024-07-12  2:31 ` dpdklab
2024-07-12  2:34 ` dpdklab
2024-07-12  2:38 ` dpdklab
2024-07-12  2:39 ` dpdklab
2024-07-12  2:39 ` |SUCCESS| " dpdklab
2024-07-12  2:39 ` |PENDING| " dpdklab
2024-07-12  2:39 ` dpdklab
2024-07-12  2:42 ` dpdklab
2024-07-12  2:43 ` dpdklab
2024-07-12  2:46 ` dpdklab
2024-07-12  2:46 ` dpdklab
2024-07-12  2:48 ` dpdklab
2024-07-12  2:49 ` dpdklab
2024-07-12  2:54 ` dpdklab
2024-07-12  2:55 ` dpdklab
2024-07-12  2:56 ` dpdklab
2024-07-12  2:59 ` dpdklab
2024-07-12  3:00 ` |SUCCESS| " dpdklab
2024-07-12  3:02 ` |PENDING| " dpdklab
2024-07-12  3:03 ` dpdklab
2024-07-12  3:03 ` dpdklab
2024-07-12  3:04 ` dpdklab
2024-07-12  3:04 ` dpdklab
2024-07-12  3:05 ` dpdklab
2024-07-12  3:05 ` dpdklab
2024-07-12  3:11 ` dpdklab
2024-07-12  3:13 ` dpdklab
2024-07-12  3:14 ` dpdklab
2024-07-12  3:15 ` |SUCCESS| " dpdklab
2024-07-12  3:18 ` |PENDING| " dpdklab
2024-07-12  3:18 ` dpdklab
2024-07-12  3:23 ` dpdklab
2024-07-12  3:24 ` dpdklab
2024-07-12  3:30 ` dpdklab
2024-07-12  3:32 ` dpdklab
2024-07-12  3:33 ` dpdklab
2024-07-12  3:35 ` dpdklab
2024-07-12  3:36 ` dpdklab
2024-07-12  3:36 ` dpdklab
2024-07-12  3:37 ` dpdklab
2024-07-12  3:40 ` dpdklab
2024-07-12  3:41 ` dpdklab
2024-07-12  3:42 ` dpdklab
2024-07-12  3:43 ` dpdklab
2024-07-12  3:44 ` dpdklab
2024-07-12  3:45 ` dpdklab
2024-07-12  3:45 ` dpdklab
2024-07-12  3:46 ` dpdklab
2024-07-12  3:46 ` dpdklab
2024-07-12  3:46 ` dpdklab
2024-07-12  3:47 ` dpdklab
2024-07-12  3:48 ` dpdklab
2024-07-12  3:50 ` dpdklab
2024-07-12  3:50 ` dpdklab
2024-07-12  3:51 ` dpdklab
2024-07-12  3:52 ` dpdklab
2024-07-12  3:53 ` dpdklab
2024-07-12  3:56 ` dpdklab
2024-07-12  3:57 ` dpdklab
2024-07-12  3:58 ` dpdklab
2024-07-12  3:59 ` dpdklab
2024-07-12  3:59 ` dpdklab
2024-07-12  4:06 ` |SUCCESS| " dpdklab
2024-07-12  4:08 ` |PENDING| " dpdklab
2024-07-12  4:08 ` dpdklab
2024-07-12  4:08 ` dpdklab
2024-07-12  4:13 ` dpdklab
2024-07-12  4:15 ` dpdklab
2024-07-12  4:18 ` |SUCCESS| " dpdklab
2024-07-12  4:28 ` |PENDING| " dpdklab
2024-07-12  4:34 ` dpdklab
2024-07-12  4:50 ` dpdklab
2024-07-12  4:56 ` dpdklab
2024-07-12  5:03 ` dpdklab
2024-07-12  5:04 ` dpdklab
2024-07-12  5:18 ` |SUCCESS| " dpdklab
2024-07-12  6:39 ` dpdklab
2024-07-12 22:48 ` dpdklab
2024-07-14  5:49 ` dpdklab [this message]
2024-07-14 12:33 ` dpdklab
2024-07-14 20:11 ` dpdklab
2024-07-14 20:24 ` 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=669366d9.050a0220.b1e25.b76dSMTPIN_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).