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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw133807-133817 [PATCH] [11/11] net/nfp: support QUEUE flo
Date: Fri, 03 Nov 2023 01:19:00 -0700 (PDT)	[thread overview]
Message-ID: <6544acf4.920a0220.502c1.319bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, November 03 2023 06:26:06 
DPDK git baseline: Repo:dpdk-next-net
  Branch: master
  CommitID:f70e8d72f9fee225d48101e96d5cef69af90afff

133807-133817 --> 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 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-03  8:19 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03  8:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08  4:54 dpdklab
2023-11-07 22:00 dpdklab
2023-11-07 21:39 dpdklab
2023-11-07 21:30 dpdklab
2023-11-07 21:27 dpdklab
2023-11-07 21:25 dpdklab
2023-11-07 21:24 dpdklab
2023-11-07 21:23 dpdklab
2023-11-07 21:22 dpdklab
2023-11-03 19:22 dpdklab
2023-11-03 19:21 dpdklab
2023-11-03 18:07 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 18:01 dpdklab
2023-11-03 17:56 dpdklab
2023-11-03 17:53 dpdklab
2023-11-03 17:47 dpdklab
2023-11-03 17:45 dpdklab
2023-11-03 17:20 dpdklab
2023-11-03 12:01 dpdklab
2023-11-03  9:26 dpdklab
2023-11-03  8:52 dpdklab
2023-11-03  8:50 dpdklab
2023-11-03  8:50 dpdklab
2023-11-03  8:49 dpdklab
2023-11-03  8:44 dpdklab
2023-11-03  8:43 dpdklab
2023-11-03  8:42 dpdklab
2023-11-03  8:41 dpdklab
2023-11-03  8:40 dpdklab
2023-11-03  8:36 dpdklab
2023-11-03  8:36 dpdklab
2023-11-03  8:36 dpdklab
2023-11-03  8:33 dpdklab
2023-11-03  8:30 dpdklab
2023-11-03  8:26 dpdklab
2023-11-03  8:25 dpdklab
2023-11-03  8:25 dpdklab
2023-11-03  8:24 dpdklab
2023-11-03  8:23 dpdklab
2023-11-03  8:23 dpdklab
2023-11-03  8:22 dpdklab
2023-11-03  8:22 dpdklab
2023-11-03  8:19 dpdklab
2023-11-03  8:18 dpdklab
2023-11-03  8:17 dpdklab
2023-11-03  8:16 dpdklab
2023-11-03  8:16 dpdklab
2023-11-03  8:14 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=6544acf4.920a0220.502c1.319bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.com \
    --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).