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| pw142292 [PATCH] [v1,1/1] fbarray: fix find_next_n for una
Date: Sun, 14 Jul 2024 17:40:43 -0700 (PDT)	[thread overview]
Message-ID: <6694700b.050a0220.54f5.a6a4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <229663bd30b1f64accf51bdefa20f6abf9ee8ad0.1720612158.git.anatoly.burakov@intel.com>

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

_Functional Testing PASS_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wednesday, July 10 2024 11:49:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:830d7c98d6b2746401142050a88ff5cbc3465ba7

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

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| scatter         |  PASS  |
+-----------------+--------+
| unit_tests_mbuf |  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 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  |
+------------+--------+


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

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-15  0:40 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <229663bd30b1f64accf51bdefa20f6abf9ee8ad0.1720612158.git.anatoly.burakov@intel.com>
2024-07-10 11:22 ` |SUCCESS| pw142292 [PATCH v1 1/1] fbarray: fix find_next_n for unaligned length qemudev
2024-07-10 11:27 ` qemudev
2024-07-10 11:50 ` |WARNING| " checkpatch
2024-07-10 12:43 ` |SUCCESS| " 0-day Robot
2024-07-10 18:10 ` |SUCCESS| pw142292 [PATCH] [v1,1/1] fbarray: fix find_next_n for una dpdklab
2024-07-10 18:15 ` dpdklab
2024-07-10 18:22 ` dpdklab
2024-07-10 18:26 ` dpdklab
2024-07-10 18:43 ` dpdklab
2024-07-10 18:44 ` dpdklab
2024-07-10 18:46 ` dpdklab
2024-07-10 18:52 ` dpdklab
2024-07-10 18:54 ` |PENDING| " dpdklab
2024-07-10 18:59 ` |SUCCESS| " dpdklab
2024-07-10 19:06 ` dpdklab
2024-07-10 19:08 ` dpdklab
2024-07-10 19:23 ` |PENDING| " dpdklab
2024-07-10 19:31 ` dpdklab
2024-07-10 19:33 ` dpdklab
2024-07-10 19:33 ` dpdklab
2024-07-10 19:34 ` dpdklab
2024-07-10 19:35 ` dpdklab
2024-07-10 19:35 ` dpdklab
2024-07-10 19:43 ` dpdklab
2024-07-10 19:44 ` dpdklab
2024-07-10 19:45 ` dpdklab
2024-07-10 19:46 ` dpdklab
2024-07-10 19:51 ` dpdklab
2024-07-10 19:53 ` dpdklab
2024-07-10 19:55 ` dpdklab
2024-07-10 19:56 ` dpdklab
2024-07-10 19:57 ` dpdklab
2024-07-10 19:58 ` |SUCCESS| " dpdklab
2024-07-10 19:59 ` dpdklab
2024-07-10 20:00 ` dpdklab
2024-07-10 20:02 ` |PENDING| " dpdklab
2024-07-10 20:05 ` dpdklab
2024-07-10 20:08 ` |SUCCESS| " dpdklab
2024-07-10 20:08 ` |PENDING| " dpdklab
2024-07-10 20:17 ` dpdklab
2024-07-10 20:22 ` dpdklab
2024-07-10 20:24 ` dpdklab
2024-07-10 20:24 ` dpdklab
2024-07-10 20:26 ` dpdklab
2024-07-10 20:26 ` dpdklab
2024-07-10 20:27 ` dpdklab
2024-07-10 20:28 ` dpdklab
2024-07-10 20:29 ` dpdklab
2024-07-10 20:30 ` dpdklab
2024-07-10 20:32 ` dpdklab
2024-07-10 20:34 ` dpdklab
2024-07-10 20:34 ` dpdklab
2024-07-10 20:38 ` dpdklab
2024-07-10 20:38 ` dpdklab
2024-07-10 20:42 ` dpdklab
2024-07-10 20:46 ` dpdklab
2024-07-10 20:50 ` dpdklab
2024-07-10 20:52 ` dpdklab
2024-07-10 21:00 ` dpdklab
2024-07-10 21:00 ` dpdklab
2024-07-10 21:01 ` dpdklab
2024-07-10 21:01 ` dpdklab
2024-07-10 21:02 ` dpdklab
2024-07-10 21:03 ` dpdklab
2024-07-10 21:06 ` dpdklab
2024-07-10 21:06 ` dpdklab
2024-07-10 21:10 ` dpdklab
2024-07-10 21:10 ` dpdklab
2024-07-10 21:11 ` dpdklab
2024-07-10 21:11 ` dpdklab
2024-07-10 21:11 ` dpdklab
2024-07-10 21:12 ` dpdklab
2024-07-10 21:12 ` dpdklab
2024-07-10 21:13 ` dpdklab
2024-07-10 21:16 ` dpdklab
2024-07-10 21:17 ` dpdklab
2024-07-10 21:19 ` dpdklab
2024-07-10 21:20 ` dpdklab
2024-07-10 21:22 ` dpdklab
2024-07-10 21:23 ` dpdklab
2024-07-10 21:24 ` dpdklab
2024-07-10 21:24 ` dpdklab
2024-07-10 21:25 ` dpdklab
2024-07-10 21:27 ` dpdklab
2024-07-10 21:28 ` dpdklab
2024-07-10 21:28 ` dpdklab
2024-07-10 21:31 ` dpdklab
2024-07-10 21:32 ` dpdklab
2024-07-10 21:32 ` dpdklab
2024-07-10 21:34 ` dpdklab
2024-07-10 21:35 ` dpdklab
2024-07-10 21:37 ` dpdklab
2024-07-10 21:42 ` dpdklab
2024-07-10 21:42 ` dpdklab
2024-07-10 21:43 ` dpdklab
2024-07-10 21:45 ` dpdklab
2024-07-10 21:46 ` dpdklab
2024-07-10 21:46 ` dpdklab
2024-07-10 21:47 ` dpdklab
2024-07-10 21:47 ` dpdklab
2024-07-10 21:58 ` dpdklab
2024-07-10 21:59 ` |SUCCESS| " dpdklab
2024-07-10 21:59 ` |PENDING| " dpdklab
2024-07-10 22:01 ` |SUCCESS| " dpdklab
2024-07-10 22:01 ` |PENDING| " dpdklab
2024-07-10 22:01 ` |SUCCESS| " dpdklab
2024-07-10 22:03 ` |PENDING| " dpdklab
2024-07-10 22:09 ` dpdklab
2024-07-10 22:10 ` |SUCCESS| " dpdklab
2024-07-10 22:12 ` |PENDING| " dpdklab
2024-07-10 22:14 ` dpdklab
2024-07-10 22:16 ` |SUCCESS| " dpdklab
2024-07-13  9:17 ` dpdklab
2024-07-14  8:00 ` dpdklab
2024-07-14 14:32 ` dpdklab
2024-07-15  0:40 ` dpdklab [this message]
2024-07-15  0:53 ` 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=6694700b.050a0220.54f5.a6a4SMTPIN_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).