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| pw131795 [PATCH] [v2] common/cnxk: reserve last LMT line f
Date: Thu, 21 Sep 2023 07:06:45 -0700 (PDT)	[thread overview]
Message-ID: <650c4df5.920a0220.6096a.3b6dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Thursday, September 21 2023 13:19:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:31e60e81f025e9fffa69b68bffe5cfaa22d5c098

131795 --> functional testing pass

Test environment and result as below:

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-21 14:06 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 14:06 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-21 21:54 dpdklab
2023-09-21 21:49 dpdklab
2023-09-21 21:38 dpdklab
2023-09-21 21:34 dpdklab
2023-09-21 15:16 dpdklab
2023-09-21 15:14 dpdklab
2023-09-21 15:12 dpdklab
2023-09-21 15:10 dpdklab
2023-09-21 15:08 dpdklab
2023-09-21 14:55 dpdklab
2023-09-21 14:51 dpdklab
2023-09-21 14:48 dpdklab
2023-09-21 14:47 dpdklab
2023-09-21 14:38 dpdklab
2023-09-21 14:31 dpdklab
2023-09-21 14:31 dpdklab
2023-09-21 14:30 dpdklab
2023-09-21 14:30 dpdklab
2023-09-21 14:30 dpdklab
2023-09-21 14:28 dpdklab
2023-09-21 14:27 dpdklab
2023-09-21 14:27 dpdklab
2023-09-21 14:27 dpdklab
2023-09-21 14:26 dpdklab
2023-09-21 14:26 dpdklab
2023-09-21 14:26 dpdklab
2023-09-21 14:26 dpdklab
2023-09-21 14:25 dpdklab
2023-09-21 14:08 dpdklab
2023-09-21 14:08 dpdklab
2023-09-21 14:07 dpdklab
2023-09-21 14:07 dpdklab
2023-09-21 14:03 dpdklab
2023-09-21 14:02 dpdklab
2023-09-21 14:01 dpdklab
2023-09-21 14:00 dpdklab
2023-09-21 13:57 dpdklab
2023-09-21 13:56 dpdklab
2023-09-21 13:56 dpdklab
2023-09-21 13:55 dpdklab
2023-09-21 13:55 dpdklab
2023-09-21 13:55 dpdklab
2023-09-21 13:54 dpdklab
2023-09-21 13:54 dpdklab
2023-09-21 13:54 dpdklab
2023-09-21 13:53 dpdklab
2023-09-21 13:53 dpdklab
2023-09-21 13:52 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=650c4df5.920a0220.6096a.3b6dSMTPIN_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).