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| pw138116 [PATCH] net/mlx5: fix the timing of releasing dro
Date: Fri, 08 Mar 2024 04:14:27 -0800 (PST)	[thread overview]
Message-ID: <65eb0123.050a0220.33b9e.c7ebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240308032237.315106-1-bingz@nvidia.com>

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

_Functional Testing PASS_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Friday, March 08 2024 03:22:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6666628362c94a0b567a39a0177539c12c97d999

138116 --> 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/29471/

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-08 12:14 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240308032237.315106-1-bingz@nvidia.com>
2024-03-08  3:00 ` |SUCCESS| pw138116 [PATCH] net/mlx5: fix the timing of releasing drop action qemudev
2024-03-08  3:05 ` qemudev
2024-03-08  3:23 ` checkpatch
2024-03-08  4:24 ` 0-day Robot
2024-03-08  7:49 ` |SUCCESS| pw138116 [PATCH] net/mlx5: fix the timing of releasing dro dpdklab
2024-03-08  7:53 ` dpdklab
2024-03-08  7:54 ` dpdklab
2024-03-08  7:56 ` dpdklab
2024-03-08  7:57 ` dpdklab
2024-03-08  8:41 ` dpdklab
2024-03-08  8:42 ` dpdklab
2024-03-08  8:43 ` dpdklab
2024-03-08  8:48 ` dpdklab
2024-03-08  8:48 ` dpdklab
2024-03-08  8:50 ` dpdklab
2024-03-08  8:51 ` dpdklab
2024-03-08  8:51 ` dpdklab
2024-03-08  8:51 ` dpdklab
2024-03-08  8:52 ` dpdklab
2024-03-08  8:52 ` dpdklab
2024-03-08  8:53 ` dpdklab
2024-03-08  8:53 ` dpdklab
2024-03-08  8:53 ` dpdklab
2024-03-08  8:56 ` dpdklab
2024-03-08  8:56 ` dpdklab
2024-03-08  8:57 ` dpdklab
2024-03-08  8:58 ` dpdklab
2024-03-08  8:58 ` dpdklab
2024-03-08  8:59 ` dpdklab
2024-03-08  8:59 ` dpdklab
2024-03-08  8:59 ` dpdklab
2024-03-08  9:00 ` dpdklab
2024-03-08  9:00 ` dpdklab
2024-03-08  9:01 ` dpdklab
2024-03-08  9:02 ` dpdklab
2024-03-08  9:02 ` dpdklab
2024-03-08  9:03 ` dpdklab
2024-03-08  9:03 ` dpdklab
2024-03-08  9:03 ` dpdklab
2024-03-08  9:03 ` dpdklab
2024-03-08  9:04 ` dpdklab
2024-03-08  9:04 ` dpdklab
2024-03-08  9:04 ` dpdklab
2024-03-08  9:04 ` dpdklab
2024-03-08  9:04 ` dpdklab
2024-03-08  9:05 ` dpdklab
2024-03-08  9:05 ` dpdklab
2024-03-08  9:06 ` dpdklab
2024-03-08  9:06 ` dpdklab
2024-03-08  9:10 ` dpdklab
2024-03-08  9:10 ` dpdklab
2024-03-08  9:11 ` dpdklab
2024-03-08  9:12 ` dpdklab
2024-03-08  9:13 ` dpdklab
2024-03-08  9:13 ` dpdklab
2024-03-08  9:13 ` dpdklab
2024-03-08  9:14 ` dpdklab
2024-03-08  9:15 ` dpdklab
2024-03-08  9:15 ` dpdklab
2024-03-08  9:16 ` dpdklab
2024-03-08  9:16 ` dpdklab
2024-03-08  9:17 ` dpdklab
2024-03-08  9:17 ` dpdklab
2024-03-08  9:18 ` dpdklab
2024-03-08  9:23 ` dpdklab
2024-03-08  9:24 ` dpdklab
2024-03-08  9:26 ` dpdklab
2024-03-08 10:07 ` dpdklab
2024-03-08 10:57 ` dpdklab
2024-03-08 12:12 ` dpdklab
2024-03-08 12:14 ` dpdklab [this message]
2024-03-08 12:25 ` dpdklab
2024-03-08 12:28 ` dpdklab
2024-03-12 21:48 ` dpdklab
2024-03-12 22:35 ` 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=65eb0123.050a0220.33b9e.c7ebSMTPIN_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).