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| pw136870-136869 [PATCH] [v8,2/2] ring: add telemetry cmd f
Date: Mon, 19 Feb 2024 01:20:51 -0800 (PST)	[thread overview]
Message-ID: <65d31d73.810a0220.2363d.96fbSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Jie Hai <haijie1@huawei.com>
Date: Monday, February 19 2024 08:32:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3cb34fb0b0adfeb163b4d0e6d5a232a21bd6f6e0

136870-136869 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-19  9:20 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  9:20 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-19 14:55 dpdklab
2024-02-19 14:41 dpdklab
2024-02-19 11:12 dpdklab
2024-02-19 11:09 dpdklab
2024-02-19 11:09 dpdklab
2024-02-19 11:08 dpdklab
2024-02-19 10:58 dpdklab
2024-02-19 10:56 dpdklab
2024-02-19 10:56 dpdklab
2024-02-19 10:49 dpdklab
2024-02-19 10:34 dpdklab
2024-02-19 10:34 dpdklab
2024-02-19 10:21 dpdklab
2024-02-19 10:09 dpdklab
2024-02-19 10:09 dpdklab
2024-02-19 10:09 dpdklab
2024-02-19 10:02 dpdklab
2024-02-19 10:02 dpdklab
2024-02-19  9:58 dpdklab
2024-02-19  9:58 dpdklab
2024-02-19  9:56 dpdklab
2024-02-19  9:55 dpdklab
2024-02-19  9:52 dpdklab
2024-02-19  9:52 dpdklab
2024-02-19  9:51 dpdklab
2024-02-19  9:49 dpdklab
2024-02-19  9:47 dpdklab
2024-02-19  9:46 dpdklab
2024-02-19  9:46 dpdklab
2024-02-19  9:45 dpdklab
2024-02-19  9:45 dpdklab
2024-02-19  9:44 dpdklab
2024-02-19  9:41 dpdklab
2024-02-19  9:41 dpdklab
2024-02-19  9:40 dpdklab
2024-02-19  9:39 dpdklab
2024-02-19  9:38 dpdklab
2024-02-19  9:37 dpdklab
2024-02-19  9:37 dpdklab
2024-02-19  9:37 dpdklab
2024-02-19  9:35 dpdklab
2024-02-19  9:34 dpdklab
2024-02-19  9:34 dpdklab
2024-02-19  9:33 dpdklab
2024-02-19  9:31 dpdklab
2024-02-19  9:31 dpdklab
2024-02-19  9:30 dpdklab
2024-02-19  9:27 dpdklab
2024-02-19  9:26 dpdklab
2024-02-19  9:25 dpdklab
2024-02-19  9:23 dpdklab
2024-02-19  9:23 dpdklab
2024-02-19  9:22 dpdklab
2024-02-19  9:21 dpdklab
2024-02-19  9:21 dpdklab
2024-02-19  9:20 dpdklab
2024-02-19  9:20 dpdklab
2024-02-19  9:19 dpdklab
2024-02-19  9:18 dpdklab
2024-02-19  9:18 dpdklab
2024-02-19  9:17 dpdklab
2024-02-19  9:17 dpdklab
2024-02-19  9:16 dpdklab
2024-02-19  9:16 dpdklab
2024-02-19  9:16 dpdklab
2024-02-19  9:15 dpdklab
2024-02-19  9:15 dpdklab
2024-02-19  9:14 dpdklab
2024-02-19  9:13 dpdklab
2024-02-19  9:13 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=65d31d73.810a0220.2363d.96fbSMTPIN_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).