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| pw137993-137994 [PATCH] [2/2] net/mlx5: apply default tuni
Date: Tue, 05 Mar 2024 07:39:43 -0800 (PST)	[thread overview]
Message-ID: <65e73cbf.050a0220.d5530.108fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240305131241.3132128-2-thomas@monjalon.net>

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

_Functional Testing PASS_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Tuesday, March 05 2024 13:12:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3472e5d3295d44b4835ffb22c39f2b7d40780f10

137993-137994 --> 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-82
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


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

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-05 15:39 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240305131241.3132128-2-thomas@monjalon.net>
2024-03-05 12:49 ` |SUCCESS| pw137993-137994 [PATCH 2/2] net/mlx5: apply default tuning to future speeds qemudev
2024-03-05 12:54 ` qemudev
2024-03-05 13:14 ` |SUCCESS| pw137994 " checkpatch
2024-03-05 14:05 ` 0-day Robot
2024-03-05 15:06 ` |SUCCESS| pw137993-137994 [PATCH] [2/2] net/mlx5: apply default tuni dpdklab
2024-03-05 15:22 ` dpdklab
2024-03-05 15:31 ` dpdklab
2024-03-05 15:31 ` dpdklab
2024-03-05 15:33 ` dpdklab
2024-03-05 15:34 ` dpdklab
2024-03-05 15:37 ` dpdklab
2024-03-05 15:39 ` dpdklab [this message]
2024-03-05 15:45 ` dpdklab
2024-03-05 15:55 ` dpdklab
2024-03-05 15:55 ` dpdklab
2024-03-05 15:56 ` dpdklab
2024-03-05 15:56 ` dpdklab
2024-03-05 15:56 ` dpdklab
2024-03-05 15:57 ` dpdklab
2024-03-05 16:05 ` dpdklab
2024-03-05 16:07 ` dpdklab
2024-03-05 16:07 ` dpdklab
2024-03-05 16:08 ` dpdklab
2024-03-05 16:09 ` dpdklab
2024-03-05 16:09 ` dpdklab
2024-03-05 16:13 ` dpdklab
2024-03-05 17:05 ` dpdklab
2024-03-05 17:06 ` dpdklab
2024-03-05 17:07 ` dpdklab
2024-03-05 17:09 ` dpdklab
2024-03-05 17:11 ` dpdklab
2024-03-05 17:12 ` dpdklab
2024-03-05 17:16 ` dpdklab
2024-03-05 17:22 ` dpdklab
2024-03-05 17:29 ` dpdklab
2024-03-05 18:17 ` dpdklab
2024-03-05 20:17 ` dpdklab
2024-03-09 14:17 ` dpdklab
2024-03-09 14:49 ` dpdklab
2024-03-09 15:22 ` 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=65e73cbf.050a0220.d5530.108fSMTPIN_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).