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| pw143584 [PATCH] [RFC] devtools/test-meson-builds: use cro
Date: Wed, 04 Sep 2024 22:22:49 -0700 (PDT)	[thread overview]
Message-ID: <66d94029.0c0a0220.38aef7.4d83SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240904140313.333098-1-bruce.richardson@intel.com>

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

_Functional Testing PASS_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, September 04 2024 14:03:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143584 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#178406

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-05  5:22 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240904140313.333098-1-bruce.richardson@intel.com>
2024-09-04 13:40 ` |SUCCESS| pw143584 [RFC PATCH] devtools/test-meson-builds: use cross file for 32bit build qemudev
2024-09-04 13:44 ` qemudev
2024-09-04 14:04 ` |WARNING| " checkpatch
2024-09-04 15:04 ` |SUCCESS| " 0-day Robot
2024-09-05  0:51 ` |SUCCESS| pw143584 [PATCH] [RFC] devtools/test-meson-builds: use cro dpdklab
2024-09-05  0:51 ` dpdklab
2024-09-05  1:00 ` dpdklab
2024-09-05  1:02 ` dpdklab
2024-09-05  1:08 ` |PENDING| " dpdklab
2024-09-05  3:27 ` |SUCCESS| " dpdklab
2024-09-05  3:31 ` dpdklab
2024-09-05  3:31 ` dpdklab
2024-09-05  3:31 ` dpdklab
2024-09-05  3:33 ` dpdklab
2024-09-05  3:34 ` dpdklab
2024-09-05  3:36 ` dpdklab
2024-09-05  3:36 ` dpdklab
2024-09-05  3:36 ` dpdklab
2024-09-05  3:37 ` dpdklab
2024-09-05  3:37 ` dpdklab
2024-09-05  3:38 ` dpdklab
2024-09-05  3:38 ` dpdklab
2024-09-05  3:42 ` dpdklab
2024-09-05  4:30 ` dpdklab
2024-09-05  4:34 ` dpdklab
2024-09-05  4:39 ` dpdklab
2024-09-05  5:22 ` dpdklab [this message]
2024-09-05  7:58 ` dpdklab
2024-09-05  8:38 ` dpdklab
2024-09-05  9:12 ` dpdklab
2024-09-05  9:14 ` dpdklab
2024-09-05  9:14 ` dpdklab
2024-09-06  6:49 ` dpdklab
2024-09-18  5:29 ` dpdklab
2024-09-18  5:40 ` 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=66d94029.0c0a0220.38aef7.4d83SMTPIN_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).