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| pw142563 [PATCH] power: fix number of uncore freqs
Date: Sat, 20 Jul 2024 20:43:35 -0700 (PDT)	[thread overview]
Message-ID: <669c83e7.050a0220.391b76.c152SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240721021806.67465-1-stephen@networkplumber.org>

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sunday, July 21 2024 02:18:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142563 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#169335

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-21  3:43 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240721021806.67465-1-stephen@networkplumber.org>
2024-07-21  2:20 ` checkpatch
2024-07-21  2:45 ` dpdklab
2024-07-21  2:48 ` dpdklab
2024-07-21  2:48 ` |PENDING| " dpdklab
2024-07-21  2:49 ` |SUCCESS| " dpdklab
2024-07-21  2:51 ` |PENDING| " dpdklab
2024-07-21  2:52 ` dpdklab
2024-07-21  2:53 ` dpdklab
2024-07-21  2:54 ` |SUCCESS| " dpdklab
2024-07-21  2:56 ` |PENDING| " dpdklab
2024-07-21  2:56 ` dpdklab
2024-07-21  2:57 ` |SUCCESS| " dpdklab
2024-07-21  2:57 ` |PENDING| " dpdklab
2024-07-21  2:58 ` |SUCCESS| " dpdklab
2024-07-21  2:58 ` |PENDING| " dpdklab
2024-07-21  2:59 ` dpdklab
2024-07-21  2:59 ` dpdklab
2024-07-21  2:59 ` dpdklab
2024-07-21  3:00 ` dpdklab
2024-07-21  3:01 ` dpdklab
2024-07-21  3:01 ` dpdklab
2024-07-21  3:02 ` dpdklab
2024-07-21  3:03 ` dpdklab
2024-07-21  3:03 ` |SUCCESS| " 0-day Robot
2024-07-21  3:04 ` |PENDING| " dpdklab
2024-07-21  3:04 ` dpdklab
2024-07-21  3:04 ` dpdklab
2024-07-21  3:05 ` dpdklab
2024-07-21  3:05 ` |SUCCESS| " dpdklab
2024-07-21  3:06 ` |PENDING| " dpdklab
2024-07-21  3:06 ` dpdklab
2024-07-21  3:06 ` |SUCCESS| " dpdklab
2024-07-21  3:07 ` |PENDING| " dpdklab
2024-07-21  3:07 ` dpdklab
2024-07-21  3:08 ` dpdklab
2024-07-21  3:08 ` dpdklab
2024-07-21  3:09 ` dpdklab
2024-07-21  3:10 ` |SUCCESS| " dpdklab
2024-07-21  3:10 ` |PENDING| " dpdklab
2024-07-21  3:10 ` dpdklab
2024-07-21  3:10 ` |SUCCESS| " dpdklab
2024-07-21  3:10 ` dpdklab
2024-07-21  3:11 ` |PENDING| " dpdklab
2024-07-21  3:11 ` dpdklab
2024-07-21  3:12 ` dpdklab
2024-07-21  3:12 ` dpdklab
2024-07-21  3:13 ` dpdklab
2024-07-21  3:14 ` dpdklab
2024-07-21  3:14 ` |SUCCESS| " dpdklab
2024-07-21  3:14 ` |PENDING| " dpdklab
2024-07-21  3:14 ` dpdklab
2024-07-21  3:16 ` dpdklab
2024-07-21  3:16 ` dpdklab
2024-07-21  3:16 ` |SUCCESS| " dpdklab
2024-07-21  3:17 ` |PENDING| " dpdklab
2024-07-21  3:18 ` dpdklab
2024-07-21  3:20 ` dpdklab
2024-07-21  3:20 ` dpdklab
2024-07-21  3:20 ` dpdklab
2024-07-21  3:22 ` dpdklab
2024-07-21  3:22 ` dpdklab
2024-07-21  3:22 ` dpdklab
2024-07-21  3:23 ` dpdklab
2024-07-21  3:25 ` dpdklab
2024-07-21  3:25 ` dpdklab
2024-07-21  3:25 ` dpdklab
2024-07-21  3:27 ` dpdklab
2024-07-21  3:28 ` dpdklab
2024-07-21  3:29 ` dpdklab
2024-07-21  3:29 ` dpdklab
2024-07-21  3:29 ` dpdklab
2024-07-21  3:30 ` dpdklab
2024-07-21  3:30 ` dpdklab
2024-07-21  3:31 ` dpdklab
2024-07-21  3:32 ` dpdklab
2024-07-21  3:32 ` dpdklab
2024-07-21  3:33 ` dpdklab
2024-07-21  3:33 ` dpdklab
2024-07-21  3:33 ` dpdklab
2024-07-21  3:34 ` dpdklab
2024-07-21  3:35 ` dpdklab
2024-07-21  3:36 ` dpdklab
2024-07-21  3:36 ` dpdklab
2024-07-21  3:37 ` dpdklab
2024-07-21  3:37 ` |SUCCESS| " dpdklab
2024-07-21  3:38 ` dpdklab
2024-07-21  3:39 ` |PENDING| " dpdklab
2024-07-21  3:39 ` |SUCCESS| " dpdklab
2024-07-21  3:42 ` |PENDING| " dpdklab
2024-07-21  3:43 ` dpdklab
2024-07-21  3:43 ` dpdklab [this message]
2024-07-21  3:44 ` dpdklab
2024-07-21  3:45 ` dpdklab
2024-07-21  3:46 ` |SUCCESS| " dpdklab
2024-07-21  3:47 ` |PENDING| " dpdklab
2024-07-21  3:48 ` dpdklab
2024-07-21  3:48 ` |SUCCESS| " dpdklab
2024-07-21  3:49 ` |PENDING| " dpdklab
2024-07-21  3:49 ` dpdklab
2024-07-21  3:49 ` dpdklab
2024-07-21  3:50 ` dpdklab
2024-07-21  3:51 ` dpdklab
2024-07-21  3:52 ` dpdklab
2024-07-21  3:53 ` dpdklab
2024-07-21  3:54 ` dpdklab
2024-07-21  3:55 ` |SUCCESS| " dpdklab
2024-07-21  3:56 ` |PENDING| " dpdklab
2024-07-21  3:57 ` dpdklab
2024-07-21  4:02 ` |SUCCESS| " dpdklab
2024-07-21  4:26 ` dpdklab
2024-07-21  4:27 ` dpdklab
2024-07-21  4:27 ` dpdklab
2024-07-22 10:56 ` qemudev
2024-07-22 10:56 ` qemudev

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=669c83e7.050a0220.391b76.c152SMTPIN_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).