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| pw142937-142942 [PATCH] [v14,6/6] dts: add API doc generat
Date: Tue, 06 Aug 2024 06:46:34 -0700 (PDT)	[thread overview]
Message-ID: <66b2293a.050a0220.1daf37.280eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240806111756.314055-7-juraj.linkes@pantheon.tech>

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

_Functional Testing PASS_

Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Tuesday, August 06 2024 11:17:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

142937-142942 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#173311

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

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

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-06 13:46 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240806111756.314055-7-juraj.linkes@pantheon.tech>
2024-08-06 10:59 ` |SUCCESS| pw142937-142942 [PATCH v14 6/6] dts: add API doc generation qemudev
2024-08-06 11:03 ` qemudev
2024-08-06 11:19 ` |WARNING| pw142942 " checkpatch
2024-08-06 13:46 ` dpdklab [this message]
2024-08-06 13:46 ` |SUCCESS| pw142937-142942 [PATCH] [v14,6/6] dts: add API doc generat dpdklab
2024-08-06 13:55 ` |PENDING| " dpdklab
2024-08-06 14:16 ` dpdklab
2024-08-06 14:23 ` |SUCCESS| pw142942 [PATCH v14 6/6] dts: add API doc generation 0-day Robot
2024-08-06 14:25 ` |PENDING| pw142937-142942 [PATCH] [v14,6/6] dts: add API doc generat dpdklab
2024-08-06 14:25 ` dpdklab
2024-08-06 14:26 ` dpdklab
2024-08-06 14:32 ` dpdklab
2024-08-06 14:32 ` dpdklab
2024-08-06 14:34 ` dpdklab
2024-08-06 14:36 ` dpdklab
2024-08-06 14:36 ` dpdklab
2024-08-06 14:37 ` dpdklab
2024-08-06 14:38 ` dpdklab
2024-08-06 14:39 ` dpdklab
2024-08-06 14:39 ` dpdklab
2024-08-06 14:40 ` dpdklab
2024-08-06 14:40 ` dpdklab
2024-08-06 14:40 ` dpdklab
2024-08-06 14:40 ` dpdklab
2024-08-06 14:41 ` dpdklab
2024-08-06 14:43 ` dpdklab
2024-08-06 14:43 ` dpdklab
2024-08-06 14:44 ` dpdklab
2024-08-06 14:44 ` dpdklab
2024-08-06 14:45 ` dpdklab
2024-08-06 14:48 ` dpdklab
2024-08-06 14:48 ` dpdklab
2024-08-06 14:50 ` dpdklab
2024-08-06 14:50 ` dpdklab
2024-08-06 14:51 ` dpdklab
2024-08-06 14:52 ` dpdklab
2024-08-06 14:58 ` dpdklab
2024-08-06 14:58 ` dpdklab
2024-08-06 15:00 ` dpdklab
2024-08-06 15:00 ` dpdklab
2024-08-06 15:03 ` dpdklab
2024-08-06 15:07 ` dpdklab
2024-08-06 15:07 ` |SUCCESS| " dpdklab
2024-08-06 15:07 ` |PENDING| " dpdklab
2024-08-06 15:07 ` dpdklab
2024-08-06 15:17 ` dpdklab
2024-08-06 15:20 ` dpdklab
2024-08-06 15:27 ` dpdklab
2024-08-06 15:27 ` |SUCCESS| " dpdklab
2024-08-06 15:28 ` |PENDING| " dpdklab
2024-08-06 15:43 ` dpdklab
2024-08-06 15:45 ` dpdklab
2024-08-06 15:48 ` |SUCCESS| " dpdklab
2024-08-06 15:53 ` dpdklab
2024-08-06 16:03 ` |PENDING| " dpdklab
2024-08-06 16:05 ` |SUCCESS| " dpdklab
2024-08-06 16:22 ` dpdklab
2024-08-07  4:22 ` dpdklab
2024-08-07  4:30 ` dpdklab
2024-08-07  4:44 ` 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=66b2293a.050a0220.1daf37.280eSMTPIN_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).