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| pw141252 [PATCH] [v3] graph: avoid id collisions
Date: Tue, 18 Jun 2024 07:19:55 -0700 (PDT)	[thread overview]
Message-ID: <6671978b.630a0220.3d25a.0985SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240618092324.54166-2-rjarry@redhat.com>

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

_Functional Testing PASS_

Submitter: Robin Jarry <rjarry@redhat.com>
Date: Tuesday, June 18 2024 09:23:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:eabbac98af1345157e07c431e18543296c37c355

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


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


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

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-18 14:20 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240618092324.54166-2-rjarry@redhat.com>
2024-06-18  8:57 ` |SUCCESS| pw141252 [PATCH v3] " qemudev
2024-06-18  9:02 ` qemudev
2024-06-18  9:25 ` |WARNING| " checkpatch
2024-06-18 10:25 ` |SUCCESS| " 0-day Robot
2024-06-18 14:05 ` |SUCCESS| pw141252 [PATCH] [v3] " dpdklab
2024-06-18 14:12 ` dpdklab
2024-06-18 14:16 ` dpdklab
2024-06-18 14:17 ` dpdklab
2024-06-18 14:19 ` dpdklab [this message]
2024-06-18 14:20 ` dpdklab
2024-06-18 14:27 ` dpdklab
2024-06-18 14:28 ` dpdklab
2024-06-18 14:30 ` dpdklab
2024-06-18 14:47 ` dpdklab
2024-06-18 14:48 ` dpdklab
2024-06-18 14:49 ` dpdklab
2024-06-18 14:52 ` dpdklab
2024-06-18 14:59 ` dpdklab
2024-06-18 15:04 ` dpdklab
2024-06-18 15:47 ` dpdklab
2024-06-18 15:48 ` dpdklab
2024-06-18 15:48 ` dpdklab
2024-06-18 15:49 ` dpdklab
2024-06-18 15:49 ` dpdklab
2024-06-18 15:50 ` dpdklab
2024-06-18 15:50 ` dpdklab
2024-06-18 15:51 ` dpdklab
2024-06-18 15:51 ` dpdklab
2024-06-18 15:52 ` dpdklab
2024-06-18 15:53 ` dpdklab
2024-06-18 15:54 ` dpdklab
2024-06-18 15:56 ` dpdklab
2024-06-18 16:08 ` dpdklab
2024-06-18 16:26 ` dpdklab
2024-06-18 16:26 ` dpdklab
2024-06-18 16:26 ` dpdklab
2024-06-18 16:27 ` dpdklab
2024-06-18 16:27 ` dpdklab
2024-06-18 16:51 ` dpdklab
2024-06-18 16:53 ` dpdklab
2024-06-18 16:54 ` dpdklab
2024-06-18 16:58 ` dpdklab
2024-06-18 17:40 ` dpdklab
2024-06-18 17:43 ` dpdklab
2024-06-18 17:46 ` dpdklab
2024-06-18 17:49 ` dpdklab
2024-06-18 17:57 ` dpdklab
2024-06-18 17:59 ` dpdklab
2024-06-18 17:59 ` dpdklab
2024-06-18 18:01 ` dpdklab
2024-06-18 18:01 ` dpdklab
2024-06-18 18:02 ` dpdklab
2024-06-18 18:08 ` dpdklab
2024-06-18 18:10 ` dpdklab
2024-06-18 18:11 ` dpdklab
2024-06-18 18:12 ` dpdklab
2024-06-18 18:12 ` dpdklab
2024-06-18 18:16 ` dpdklab
2024-06-18 18:17 ` dpdklab
2024-06-18 18:17 ` dpdklab
2024-06-18 18:23 ` dpdklab
2024-06-18 18:23 ` dpdklab
2024-06-18 18:25 ` dpdklab
2024-06-18 18:25 ` dpdklab
2024-06-18 18:27 ` dpdklab
2024-06-18 18:28 ` dpdklab
2024-06-18 18:53 ` dpdklab
2024-06-18 18:55 ` dpdklab
2024-06-18 18:55 ` dpdklab
2024-06-18 18:59 ` dpdklab
2024-06-18 19:01 ` dpdklab
2024-06-18 19:03 ` dpdklab
2024-06-18 19:03 ` dpdklab
2024-06-18 19:05 ` dpdklab
2024-06-18 19:06 ` dpdklab
2024-06-18 19:10 ` dpdklab
2024-06-18 19:10 ` dpdklab
2024-06-18 19:11 ` dpdklab
2024-06-18 19:12 ` dpdklab
2024-06-18 19:13 ` dpdklab
2024-06-18 19:14 ` dpdklab
2024-06-18 19:14 ` dpdklab
2024-06-18 19:15 ` dpdklab
2024-06-18 19:16 ` dpdklab
2024-06-18 19:16 ` dpdklab
2024-06-18 19:17 ` dpdklab
2024-06-18 19:18 ` dpdklab
2024-06-18 19:19 ` dpdklab
2024-06-18 19:20 ` dpdklab
2024-06-18 19:20 ` dpdklab
2024-06-18 19:28 ` dpdklab
2024-06-18 19:33 ` dpdklab
2024-06-18 19:33 ` dpdklab
2024-06-18 19:35 ` dpdklab
2024-06-18 19:36 ` dpdklab
2024-06-18 19:38 ` dpdklab
2024-06-18 19:38 ` dpdklab
2024-06-18 19:39 ` dpdklab
2024-06-18 19:40 ` dpdklab
2024-06-18 20:08 ` dpdklab
2024-06-18 20:09 ` dpdklab
2024-06-18 20:14 ` dpdklab
2024-06-18 20:15 ` dpdklab
2024-06-18 20:17 ` dpdklab
2024-06-18 20:18 ` dpdklab
2024-06-18 20:20 ` dpdklab
2024-06-18 20:27 ` dpdklab
2024-06-18 20:31 ` dpdklab
2024-06-18 21:12 ` dpdklab
2024-06-18 21:30 ` dpdklab
2024-06-19  3:10 ` dpdklab
2024-06-19  3:50 ` dpdklab
2024-06-19 22: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=6671978b.630a0220.3d25a.0985SMTPIN_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).