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| pw141735-141737 [PATCH] [v7,3/3] dts: config schema
Date: Tue, 25 Jun 2024 17:53:08 -0700 (PDT)	[thread overview]
Message-ID: <667b6674.050a0220.94daf.27a0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240625153324.27257-3-dmarx@iol.unh.edu>

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

_Functional Testing PASS_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Tuesday, June 25 2024 15:33:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9ab7baa5c14b1ba928c09bda4734827d6d367d6b

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


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


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

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-26  0:53 UTC|newest]

Thread overview: 132+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240625153324.27257-3-dmarx@iol.unh.edu>
2024-06-25 15:08 ` |SUCCESS| pw141735-141737 [PATCH v7 3/3] " qemudev
2024-06-25 15:13 ` qemudev
2024-06-25 15:36 ` |SUCCESS| pw141737 " checkpatch
2024-06-25 16:25 ` 0-day Robot
2024-06-25 23:36 ` |SUCCESS| pw141735-141737 [PATCH] [v7,3/3] " dpdklab
2024-06-25 23:37 ` dpdklab
2024-06-25 23:37 ` dpdklab
2024-06-25 23:42 ` dpdklab
2024-06-25 23:42 ` dpdklab
2024-06-25 23:42 ` dpdklab
2024-06-25 23:43 ` dpdklab
2024-06-25 23:56 ` dpdklab
2024-06-25 23:56 ` dpdklab
2024-06-25 23:57 ` dpdklab
2024-06-25 23:57 ` dpdklab
2024-06-25 23:58 ` dpdklab
2024-06-25 23:58 ` dpdklab
2024-06-26  0:05 ` |PENDING| " dpdklab
2024-06-26  0:05 ` dpdklab
2024-06-26  0:05 ` dpdklab
2024-06-26  0:06 ` dpdklab
2024-06-26  0:06 ` dpdklab
2024-06-26  0:06 ` dpdklab
2024-06-26  0:07 ` dpdklab
2024-06-26  0:07 ` dpdklab
2024-06-26  0:08 ` dpdklab
2024-06-26  0:08 ` dpdklab
2024-06-26  0:09 ` dpdklab
2024-06-26  0:09 ` dpdklab
2024-06-26  0:10 ` dpdklab
2024-06-26  0:11 ` dpdklab
2024-06-26  0:11 ` dpdklab
2024-06-26  0:11 ` dpdklab
2024-06-26  0:46 ` |SUCCESS| " dpdklab
2024-06-26  0:51 ` dpdklab
2024-06-26  0:53 ` dpdklab [this message]
2024-06-26  1:06 ` dpdklab
2024-06-26  1:08 ` dpdklab
2024-06-26  1:08 ` dpdklab
2024-06-26  1:08 ` dpdklab
2024-06-26  1:09 ` dpdklab
2024-06-26  1:10 ` dpdklab
2024-06-26  1:10 ` dpdklab
2024-06-26  1:11 ` dpdklab
2024-06-26  1:12 ` dpdklab
2024-06-26  1:13 ` dpdklab
2024-06-26  1:13 ` dpdklab
2024-06-26  1:14 ` dpdklab
2024-06-26  1:14 ` dpdklab
2024-06-26  1:15 ` dpdklab
2024-06-26  1:15 ` dpdklab
2024-06-26  1:15 ` dpdklab
2024-06-26  1:16 ` dpdklab
2024-06-26  1:16 ` dpdklab
2024-06-26  1:17 ` dpdklab
2024-06-26  1:17 ` dpdklab
2024-06-26  1:17 ` dpdklab
2024-06-26  1:17 ` dpdklab
2024-06-26  1:17 ` dpdklab
2024-06-26  1:19 ` dpdklab
2024-06-26  1:19 ` dpdklab
2024-06-26  1:24 ` dpdklab
2024-06-26  1:25 ` dpdklab
2024-06-26  1:27 ` dpdklab
2024-06-26  1:28 ` dpdklab
2024-06-26  1:29 ` dpdklab
2024-06-26  1:29 ` dpdklab
2024-06-26  1:31 ` dpdklab
2024-06-26  1:43 ` dpdklab
2024-06-26  1:43 ` dpdklab
2024-06-26  1:43 ` dpdklab
2024-06-26  1:44 ` dpdklab
2024-06-26  1:44 ` dpdklab
2024-06-26  1:45 ` dpdklab
2024-06-26  1:45 ` dpdklab
2024-06-26  1:46 ` dpdklab
2024-06-26  1:46 ` dpdklab
2024-06-26  1:46 ` dpdklab
2024-06-26  1:47 ` dpdklab
2024-06-26  1:47 ` dpdklab
2024-06-26  1:53 ` dpdklab
2024-06-26  1:54 ` dpdklab
2024-06-26  1:54 ` dpdklab
2024-06-26  1:54 ` dpdklab
2024-06-26  1:55 ` dpdklab
2024-06-26  1:55 ` dpdklab
2024-06-26  1:57 ` dpdklab
2024-06-26  1:57 ` dpdklab
2024-06-26  1:57 ` dpdklab
2024-06-26  1:57 ` dpdklab
2024-06-26  1:58 ` dpdklab
2024-06-26  1:59 ` dpdklab
2024-06-26  2:00 ` dpdklab
2024-06-26  2:00 ` dpdklab
2024-06-26  2:08 ` dpdklab
2024-06-26  2:09 ` dpdklab
2024-06-26  2:09 ` dpdklab
2024-06-26  2:10 ` dpdklab
2024-06-26  2:10 ` dpdklab
2024-06-26  2:10 ` dpdklab
2024-06-26  2:10 ` dpdklab
2024-06-26  2:10 ` dpdklab
2024-06-26  2:11 ` dpdklab
2024-06-26  2:16 ` dpdklab
2024-06-26  2:33 ` dpdklab
2024-06-26  2:38 ` dpdklab
2024-06-26  2:40 ` dpdklab
2024-06-26  2:40 ` dpdklab
2024-06-26  2:44 ` dpdklab
2024-06-26  2:44 ` dpdklab
2024-06-26  2:45 ` dpdklab
2024-06-26  2:45 ` dpdklab
2024-06-26  2:46 ` dpdklab
2024-06-26  2:47 ` dpdklab
2024-06-26  2:48 ` dpdklab
2024-06-26  2:48 ` dpdklab
2024-06-26  2:48 ` dpdklab
2024-06-26  2:50 ` dpdklab
2024-06-26  2:52 ` dpdklab
2024-06-26  2:53 ` dpdklab
2024-06-26  2:55 ` dpdklab
2024-06-26  2:56 ` dpdklab
2024-06-26  2:59 ` dpdklab
2024-06-26  2:59 ` dpdklab
2024-06-26  3:02 ` dpdklab
2024-06-26  3:02 ` dpdklab
2024-06-26  3:03 ` dpdklab
2024-06-26  3:03 ` dpdklab
2024-06-26  3:04 ` dpdklab
2024-06-26  3:06 ` dpdklab
2024-06-26  3:25 ` dpdklab
2024-06-26  4:11 ` 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=667b6674.050a0220.94daf.27a0SMTPIN_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).