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| pw135819 [PATCH] testpmd: do not print bitrate-stats in he
Date: Tue, 09 Jan 2024 16:12:21 -0800 (PST)	[thread overview]
Message-ID: <659de0e5.050a0220.83036.8516SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, January 09 2024 23:09:27 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871

135819 --> functional testing pass

Test environment and result as below:

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


Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-10  0:12 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10  0:12 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-10  1:13 dpdklab
2024-01-10  0:51 dpdklab
2024-01-10  0:46 dpdklab
2024-01-10  0:43 dpdklab
2024-01-10  0:41 dpdklab
2024-01-10  0:38 dpdklab
2024-01-10  0:34 dpdklab
2024-01-10  0:31 dpdklab
2024-01-10  0:31 dpdklab
2024-01-10  0:30 dpdklab
2024-01-10  0:30 dpdklab
2024-01-10  0:19 dpdklab
2024-01-10  0:18 dpdklab
2024-01-10  0:18 dpdklab
2024-01-10  0:18 dpdklab
2024-01-10  0:18 dpdklab
2024-01-10  0:17 dpdklab
2024-01-10  0:17 dpdklab
2024-01-10  0:17 dpdklab
2024-01-10  0:16 dpdklab
2024-01-10  0:15 dpdklab
2024-01-10  0:15 dpdklab
2024-01-10  0:15 dpdklab
2024-01-10  0:15 dpdklab
2024-01-10  0:14 dpdklab
2024-01-10  0:14 dpdklab
2024-01-10  0:14 dpdklab
2024-01-10  0:13 dpdklab
2024-01-10  0:13 dpdklab
2024-01-10  0:13 dpdklab
2024-01-10  0:12 dpdklab
2024-01-10  0:12 dpdklab
2024-01-10  0:12 dpdklab
2024-01-10  0:12 dpdklab
2024-01-10  0:11 dpdklab
2024-01-10  0:11 dpdklab
2024-01-10  0:11 dpdklab
2024-01-10  0:11 dpdklab
2024-01-10  0:10 dpdklab
2024-01-10  0:10 dpdklab
2024-01-10  0:10 dpdklab
2024-01-10  0:09 dpdklab
2024-01-10  0:09 dpdklab
2024-01-10  0:09 dpdklab
2024-01-10  0:08 dpdklab
2024-01-10  0:06 dpdklab
2024-01-10  0:06 dpdklab
2024-01-10  0:06 dpdklab
2024-01-10  0:06 dpdklab
2024-01-10  0:05 dpdklab
2024-01-10  0:05 dpdklab
2024-01-10  0:05 dpdklab
2024-01-10  0:04 dpdklab
2024-01-10  0:04 dpdklab
2024-01-10  0:04 dpdklab
2024-01-10  0:04 dpdklab
2024-01-10  0:03 dpdklab
2024-01-10  0:03 dpdklab
2024-01-10  0:03 dpdklab
2024-01-10  0:03 dpdklab
2024-01-10  0:03 dpdklab
2024-01-10  0:02 dpdklab
2024-01-10  0:02 dpdklab
2024-01-10  0:02 dpdklab
2024-01-10  0:01 dpdklab
2024-01-09 23:54 dpdklab
2024-01-09 23:53 dpdklab
2024-01-09 23:53 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=659de0e5.050a0220.83036.8516SMTPIN_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).