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| pw138412 [PATCH] app/testpmd: fix unpassed RSS algorithm
Date: Mon, 18 Mar 2024 19:23:49 -0700 (PDT)	[thread overview]
Message-ID: <65f8f735.0d0a0220.27645.2d8aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240315030054.2976598-1-haijie1@huawei.com>

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

_Functional Testing PASS_

Submitter: Jie Hai <haijie1@huawei.com>
Date: Friday, March 15 2024 03:00:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:136cbcbe91ea5d7bdb337b168947828947647b45

138412 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
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.83+
Compiler: gcc 11.4.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/1


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
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2024-03-19  2:23 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240315030054.2976598-1-haijie1@huawei.com>
2024-03-15  2:43 ` qemudev
2024-03-15  2:48 ` qemudev
2024-03-15  3:06 ` checkpatch
2024-03-15  4:43 ` 0-day Robot
2024-03-15  7:10 ` dpdklab
2024-03-15  7:11 ` dpdklab
2024-03-15  7:15 ` dpdklab
2024-03-15  7:17 ` dpdklab
2024-03-15  7:17 ` dpdklab
2024-03-15  7:18 ` dpdklab
2024-03-15  7:19 ` dpdklab
2024-03-15  7:19 ` dpdklab
2024-03-15  7:19 ` dpdklab
2024-03-15  7:20 ` dpdklab
2024-03-15  7:20 ` dpdklab
2024-03-15  7:21 ` dpdklab
2024-03-15  7:22 ` dpdklab
2024-03-15  7:22 ` dpdklab
2024-03-15  7:45 ` dpdklab
2024-03-15  7:51 ` dpdklab
2024-03-15  7:58 ` dpdklab
2024-03-15  7:59 ` dpdklab
2024-03-15  8:00 ` dpdklab
2024-03-15  8:03 ` dpdklab
2024-03-15  8:03 ` dpdklab
2024-03-15  8:04 ` dpdklab
2024-03-15  8:04 ` dpdklab
2024-03-15  8:05 ` dpdklab
2024-03-15  8:05 ` dpdklab
2024-03-15  8:06 ` dpdklab
2024-03-15  8:06 ` dpdklab
2024-03-15  8:06 ` dpdklab
2024-03-15  8:06 ` dpdklab
2024-03-15  8:07 ` dpdklab
2024-03-15  8:07 ` dpdklab
2024-03-15  8:07 ` dpdklab
2024-03-15  8:07 ` dpdklab
2024-03-15  8:07 ` dpdklab
2024-03-15  8:08 ` dpdklab
2024-03-15  8:09 ` dpdklab
2024-03-15  8:10 ` dpdklab
2024-03-15  8:11 ` dpdklab
2024-03-15  8:11 ` dpdklab
2024-03-15  8:11 ` dpdklab
2024-03-15  8:12 ` dpdklab
2024-03-15  8:12 ` dpdklab
2024-03-15  8:13 ` dpdklab
2024-03-15  8:14 ` dpdklab
2024-03-15  8:14 ` dpdklab
2024-03-15  8:14 ` dpdklab
2024-03-15  8:15 ` dpdklab
2024-03-15  8:16 ` dpdklab
2024-03-15  8:16 ` dpdklab
2024-03-15  8:18 ` dpdklab
2024-03-15  8:29 ` dpdklab
2024-03-15  8:31 ` dpdklab
2024-03-15  8:34 ` dpdklab
2024-03-15  8:35 ` dpdklab
2024-03-15  8:35 ` dpdklab
2024-03-15  8:36 ` dpdklab
2024-03-15  8:36 ` dpdklab
2024-03-15  8:36 ` dpdklab
2024-03-15  8:37 ` dpdklab
2024-03-15  8:37 ` dpdklab
2024-03-15  8:37 ` dpdklab
2024-03-15  8:39 ` dpdklab
2024-03-15  8:39 ` dpdklab
2024-03-15  8:40 ` dpdklab
2024-03-15  8:41 ` dpdklab
2024-03-15  8:42 ` dpdklab
2024-03-15  8:43 ` dpdklab
2024-03-15  8:43 ` dpdklab
2024-03-15  8:53 ` dpdklab
2024-03-15  9:13 ` dpdklab
2024-03-15  9:20 ` dpdklab
2024-03-15  9:51 ` dpdklab
2024-03-19  1:47 ` dpdklab
2024-03-19  2:23 ` dpdklab [this message]

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=65f8f735.0d0a0220.27645.2d8aSMTPIN_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).