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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126429-126433 [PATCH] [v1, 5/5] ml/cnxk: implement xstats driver functions
Date: Sat, 22 Apr 2023 23:19:33 -0700 (PDT)	[thread overview]
Message-ID: <6444cdf5.0d0a0220.1ee51.6e8eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Sunday, April 23 2023 05:14:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5f34cc454df420b9b2da8deb949fb76cba058b87

126429-126433 --> 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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-23  6:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23  6:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-23  9:45 dpdklab
2023-04-23  8:57 dpdklab
2023-04-23  8:56 dpdklab
2023-04-23  8:56 dpdklab
2023-04-23  8:24 dpdklab
2023-04-23  8:03 dpdklab
2023-04-23  8:03 dpdklab
2023-04-23  8:01 dpdklab
2023-04-23  7:48 dpdklab
2023-04-23  7:46 dpdklab
2023-04-23  7:46 dpdklab
2023-04-23  7:45 dpdklab
2023-04-23  7:36 dpdklab
2023-04-23  7:36 dpdklab
2023-04-23  7:33 dpdklab
2023-04-23  7:25 dpdklab
2023-04-23  6:56 dpdklab
2023-04-23  6:47 dpdklab
2023-04-23  6:38 dpdklab
2023-04-23  6:34 dpdklab
2023-04-23  6:33 dpdklab
2023-04-23  6:33 dpdklab
2023-04-23  6:31 dpdklab
2023-04-23  6:29 dpdklab
2023-04-23  6:19 dpdklab
2023-04-23  6:17 dpdklab
2023-04-23  6:16 dpdklab
2023-04-23  6:11 dpdklab
     [not found] <20230423051403.31971-6-syalavarthi@marvell.com>
2023-04-23  5:05 ` |SUCCESS| pw126429-126433 [PATCH v1 " qemudev
2023-04-23  5:09 ` qemudev

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=6444cdf5.0d0a0220.1ee51.6e8eSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).