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| pw143743-143745 [PATCH] [RFC,v2,3/3] vduse: use import VDU
Date: Fri, 06 Sep 2024 20:54:49 -0700 (PDT)	[thread overview]
Message-ID: <66dbce89.050a0220.4373b.1ce1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906152337.2805036-4-maxime.coquelin@redhat.com>

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

_Functional Testing PASS_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Friday, September 06 2024 15:23:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143743-143745 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#179009

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

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-07  3:54 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906152337.2805036-4-maxime.coquelin@redhat.com>
2024-09-06 16:24 ` |SUCCESS| pw143745 [RFC v2 3/3] vduse: use import VDUSE uAPI header 0-day Robot
2024-09-06 17:02 ` |SUCCESS| pw143743-143745 [PATCH] [RFC,v2,3/3] vduse: use import VDU dpdklab
2024-09-06 17:12 ` dpdklab
2024-09-06 17:13 ` dpdklab
2024-09-06 17:14 ` dpdklab
2024-09-06 17:22 ` dpdklab
2024-09-06 17:36 ` |PENDING| " dpdklab
2024-09-06 17:56 ` |SUCCESS| " dpdklab
2024-09-06 18:13 ` dpdklab
2024-09-06 18:16 ` dpdklab
2024-09-06 18:17 ` dpdklab
2024-09-06 18:18 ` dpdklab
2024-09-06 18:19 ` dpdklab
2024-09-06 18:20 ` dpdklab
2024-09-06 18:21 ` dpdklab
2024-09-06 18:25 ` |PENDING| " dpdklab
2024-09-06 18:30 ` |SUCCESS| " dpdklab
2024-09-06 18:35 ` |PENDING| " dpdklab
2024-09-06 21:16 ` |SUCCESS| " dpdklab
2024-09-06 21:48 ` dpdklab
2024-09-06 21:58 ` dpdklab
2024-09-06 22:18 ` dpdklab
2024-09-06 23:51 ` dpdklab
2024-09-07  0:51 ` dpdklab
2024-09-07  3:03 ` dpdklab
2024-09-07  3:07 ` dpdklab
2024-09-07  3:11 ` dpdklab
2024-09-07  3:15 ` dpdklab
2024-09-07  3:35 ` dpdklab
2024-09-07  3:42 ` dpdklab
2024-09-07  3:46 ` dpdklab
2024-09-07  3:50 ` dpdklab
2024-09-07  3:54 ` dpdklab [this message]
2024-09-07  4:14 ` dpdklab
2024-09-07  8:26 ` dpdklab
2024-09-07  9:00 ` dpdklab
2024-09-07  9:14 ` |PENDING| " dpdklab
2024-09-07 12:18 ` |SUCCESS| " dpdklab
2024-09-07 15:07 ` dpdklab
2024-09-07 15:36 ` dpdklab
2024-09-07 16:07 ` dpdklab
2024-09-08  3:35 ` dpdklab
2024-09-08  4:02 ` dpdklab
2024-09-17  6:51 ` dpdklab
2024-09-17  7:11 ` dpdklab
2024-09-17  7:34 ` dpdklab
2024-09-17  7:43 ` 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=66dbce89.050a0220.4373b.1ce1SMTPIN_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).