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| pw125212-125218 [PATCH] [v3, 8/8] ml/cnxk: reduce levels of nested variables access
Date: Thu, 16 Mar 2023 23:20:40 +0000 (UTC)	[thread overview]
Message-ID: <20230316232040.588F56011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Functional Testing PASS_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Thursday, March 16 2023 21:29:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:bb1f2f5b181b9d8ea7fb28ca2024914fc57bd823

125212-125218 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-16 23:20 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 23:20 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-19 18:53 dpdklab
2023-03-19 18:53 dpdklab
2023-03-19 18:49 dpdklab
2023-03-19 18:44 dpdklab
2023-03-19 18:44 dpdklab
2023-03-19 18:32 dpdklab
2023-03-19 18:31 dpdklab
2023-03-19 18:27 dpdklab
2023-03-19 18:21 dpdklab
2023-03-19 18:13 dpdklab
2023-03-19 18:10 dpdklab
2023-03-19 18:06 dpdklab
2023-03-19 18:05 dpdklab
2023-03-19 18:04 dpdklab
2023-03-19 17:55 dpdklab
2023-03-19 17:53 dpdklab
2023-03-19 17:50 dpdklab
2023-03-19 17:47 dpdklab
2023-03-19 17:38 dpdklab
2023-03-19 17:37 dpdklab
2023-03-19 17:37 dpdklab
2023-03-19 17:36 dpdklab
2023-03-19 17:34 dpdklab
2023-03-19 17:22 dpdklab
2023-03-19 17:20 dpdklab
2023-03-19 17:18 dpdklab
2023-03-19 16:42 dpdklab
2023-03-19  7:55 dpdklab
2023-03-19  7:11 dpdklab
2023-03-19  3:29 dpdklab
2023-03-19  3:23 dpdklab
2023-03-17  5:12 dpdklab
2023-03-17  5:08 dpdklab
2023-03-17  3:46 dpdklab
2023-03-17  3:44 dpdklab
2023-03-17  3:35 dpdklab
2023-03-17  3:14 dpdklab
2023-03-17  3:01 dpdklab
2023-03-17  2:49 dpdklab
2023-03-17  1:40 dpdklab
2023-03-17  1:28 dpdklab
2023-03-17  1:11 dpdklab
2023-03-17  0:54 dpdklab
2023-03-17  0:13 dpdklab
2023-03-17  0:07 dpdklab
2023-03-17  0:04 dpdklab
2023-03-17  0:03 dpdklab
2023-03-16 23:58 dpdklab
2023-03-16 23:58 dpdklab
2023-03-16 23:51 dpdklab
2023-03-16 23:48 dpdklab
2023-03-16 23:44 dpdklab
2023-03-16 23:39 dpdklab
2023-03-16 23:13 dpdklab
2023-03-16 23:12 dpdklab
2023-03-16 23:00 dpdklab
     [not found] <20230316212904.9318-9-syalavarthi@marvell.com>
2023-03-16 21:19 ` |SUCCESS| pw125212-125218 [PATCH v3 " qemudev
2023-03-16 21:23 ` 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=20230316232040.588F56011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --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).