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| pw134111-134110 [PATCH] [v2,3/3] app/testpmd: fix unnecess
Date: Fri, 10 Nov 2023 23:05:44 -0800 (PST)	[thread overview]
Message-ID: <654f27c8.050a0220.9765d.03dbSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Huisong Li <lihuisong@huawei.com>
Date: Saturday, November 11 2023 04:59:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa6a754e746551382922c8be4db0e8f8e39bab40

134111-134110 --> functional testing pass

Test environment and result as below:

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-11  7:05 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11  7:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-15  0:10 dpdklab
2023-11-14 23:48 dpdklab
2023-11-11 10:39 dpdklab
2023-11-11  9:04 dpdklab
2023-11-11  9:01 dpdklab
2023-11-11  8:55 dpdklab
2023-11-11  8:52 dpdklab
2023-11-11  8:50 dpdklab
2023-11-11  8:50 dpdklab
2023-11-11  8:46 dpdklab
2023-11-11  8:46 dpdklab
2023-11-11  8:42 dpdklab
2023-11-11  8:41 dpdklab
2023-11-11  8:39 dpdklab
2023-11-11  8:37 dpdklab
2023-11-11  8:35 dpdklab
2023-11-11  8:35 dpdklab
2023-11-11  8:34 dpdklab
2023-11-11  8:33 dpdklab
2023-11-11  8:31 dpdklab
2023-11-11  8:30 dpdklab
2023-11-11  8:28 dpdklab
2023-11-11  8:27 dpdklab
2023-11-11  8:27 dpdklab
2023-11-11  8:26 dpdklab
2023-11-11  8:25 dpdklab
2023-11-11  8:24 dpdklab
2023-11-11  8:23 dpdklab
2023-11-11  8:21 dpdklab
2023-11-11  8:20 dpdklab
2023-11-11  8:08 dpdklab
2023-11-11  8:07 dpdklab
2023-11-11  7:56 dpdklab
2023-11-11  7:56 dpdklab
2023-11-11  7:51 dpdklab
2023-11-11  7:46 dpdklab
2023-11-11  7:32 dpdklab
2023-11-11  7:17 dpdklab
2023-11-11  7:15 dpdklab
2023-11-11  7:12 dpdklab
2023-11-11  7:12 dpdklab
2023-11-11  7:11 dpdklab
2023-11-11  7:10 dpdklab
2023-11-11  7:09 dpdklab
2023-11-11  7:09 dpdklab
2023-11-11  7:08 dpdklab
2023-11-11  7:08 dpdklab
2023-11-11  7:08 dpdklab
2023-11-11  7:07 dpdklab
2023-11-11  7:07 dpdklab
2023-11-11  7:05 dpdklab
2023-11-11  7:03 dpdklab
2023-11-11  7:02 dpdklab
2023-11-11  7:01 dpdklab
2023-11-11  7:00 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=654f27c8.050a0220.9765d.03dbSMTPIN_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).