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| pw143766-143767 [PATCH] [2/2] eal: detect supported driver
Date: Tue, 10 Sep 2024 04:21:07 -0700 (PDT)	[thread overview]
Message-ID: <66e02ba3.c80a0220.1ad7c0.0defSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906210637.630356-2-wathsala.vithanage@arm.com>

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

_Functional Testing PASS_

Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Friday, September 06 2024 21:06:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143766-143767 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#179514

Test environment and result as below:

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/30955/

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-10 11:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906210637.630356-2-wathsala.vithanage@arm.com>
2024-09-06 20:47 ` |SUCCESS| pw143766-143767 [PATCH 2/2] " qemudev
2024-09-06 20:52 ` qemudev
2024-09-06 21:08 ` |SUCCESS| pw143767 " checkpatch
2024-09-06 22:05 ` 0-day Robot
2024-09-10  2:12 ` |SUCCESS| pw143766-143767 [PATCH] [2/2] " dpdklab
2024-09-10  2:18 ` dpdklab
2024-09-10  2:23 ` dpdklab
2024-09-10  3:50 ` |PENDING| " dpdklab
2024-09-10  3:59 ` |SUCCESS| " dpdklab
2024-09-10  3:59 ` dpdklab
2024-09-10  4:01 ` dpdklab
2024-09-10  4:09 ` |PENDING| " dpdklab
2024-09-10  4:31 ` dpdklab
2024-09-10  5:13 ` |SUCCESS| " dpdklab
2024-09-10  7:53 ` dpdklab
2024-09-10  8:24 ` dpdklab
2024-09-10  8:26 ` dpdklab
2024-09-10  9:15 ` dpdklab
2024-09-10  9:15 ` dpdklab
2024-09-10 11:11 ` dpdklab
2024-09-10 11:16 ` dpdklab
2024-09-10 11:21 ` dpdklab [this message]
2024-09-10 11:25 ` dpdklab
2024-09-10 11:45 ` dpdklab
2024-09-10 16:12 ` dpdklab
2024-09-16  5:56 ` dpdklab
2024-09-16 12:54 ` 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=66e02ba3.c80a0220.1ad7c0.0defSMTPIN_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).