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| pw143918-143933 [PATCH] [v2,19/19] net/xsc: add dev basic
Date: Wed, 11 Sep 2024 09:09:52 -0700 (PDT)	[thread overview]
Message-ID: <66e1c0d0.170a0220.274fb4.0d01SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240911020740.3950704-20-wanry@yunsilicon.com>

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

_Functional Testing PASS_

Submitter: WanRenyong <wanry@yunsilicon.com>
Date: Wednesday, September 11 2024 02:07:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:523fd7b3adfdf5a87651e8ca33bc69223b3211d5

143918-143933 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#179837

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

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-11 16:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240911020740.3950704-20-wanry@yunsilicon.com>
2024-09-11  1:44 ` |FAILURE| pw143918-143933 [PATCH v2 19/19] net/xsc: add dev basic stats ops qemudev
2024-09-11  2:10 ` |WARNING| pw143933 " checkpatch
2024-09-11  2:56 ` |SUCCESS| pw143918-143933 [PATCH] [v2,19/19] net/xsc: add dev basic dpdklab
2024-09-11  3:00 ` dpdklab
2024-09-11  3:04 ` |FAILURE| pw143933 [PATCH v2 19/19] net/xsc: add dev basic stats ops 0-day Robot
2024-09-11  3:39 ` |SUCCESS| pw143918-143933 [PATCH] [v2,19/19] net/xsc: add dev basic dpdklab
2024-09-11  6:33 ` |PENDING| " dpdklab
2024-09-11  6:41 ` dpdklab
2024-09-11  6:49 ` |SUCCESS| " dpdklab
2024-09-11  6:49 ` dpdklab
2024-09-11  6:50 ` dpdklab
2024-09-11  7:08 ` |PENDING| " dpdklab
2024-09-11  8:33 ` |SUCCESS| " dpdklab
2024-09-11  9:48 ` dpdklab
2024-09-11 10:00 ` dpdklab
2024-09-11 11:16 ` |PENDING| " dpdklab
2024-09-11 15:38 ` |SUCCESS| " dpdklab
2024-09-11 15:42 ` dpdklab
2024-09-11 15:42 ` dpdklab
2024-09-11 15:46 ` dpdklab
2024-09-11 16:05 ` dpdklab
2024-09-11 16:09 ` dpdklab [this message]
2024-09-11 17:00 ` dpdklab
2024-09-11 17:46 ` dpdklab
2024-09-11 19:40 ` dpdklab
2024-09-15 19:58 ` dpdklab
2024-09-16  1:22 ` 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=66e1c0d0.170a0220.274fb4.0d01SMTPIN_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).