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| pw137648-137649 [PATCH] [v2,2/2] common/cnxk: fix possible
Date: Fri, 01 Mar 2024 16:03:12 -0800 (PST)	[thread overview]
Message-ID: <65e26cc0.050a0220.a42a2.e37cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301033534.1968900-2-psatheesh@marvell.com>

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

_Functional Testing PASS_

Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Friday, March 01 2024 03:35:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ce8ce20ae46fe0df7632a0172c73d2dcd1ac0187

137648-137649 --> 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/29357/

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-02  0:03 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301033534.1968900-2-psatheesh@marvell.com>
2024-03-01  3:13 ` |SUCCESS| pw137648-137649 [PATCH v2 2/2] common/cnxk: fix possible out-of-bounds access qemudev
2024-03-01  3:17 ` qemudev
2024-03-01  3:37 ` |SUCCESS| pw137649 " checkpatch
2024-03-01  4:25 ` |SUCCESS| pw137649 [dpdk-dev] " 0-day Robot
2024-03-01 22:37 ` |SUCCESS| pw137648-137649 [PATCH] [v2,2/2] common/cnxk: fix possible dpdklab
2024-03-01 22:45 ` dpdklab
2024-03-01 23:05 ` dpdklab
2024-03-01 23:14 ` dpdklab
2024-03-01 23:16 ` dpdklab
2024-03-01 23:16 ` dpdklab
2024-03-01 23:17 ` dpdklab
2024-03-01 23:18 ` dpdklab
2024-03-01 23:18 ` dpdklab
2024-03-01 23:19 ` dpdklab
2024-03-01 23:20 ` dpdklab
2024-03-01 23:20 ` dpdklab
2024-03-01 23:21 ` dpdklab
2024-03-01 23:24 ` dpdklab
2024-03-01 23:24 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:59 ` dpdklab
2024-03-02  0:01 ` dpdklab
2024-03-02  0:03 ` dpdklab [this message]
2024-03-02  0:05 ` dpdklab
2024-03-02  1:54 ` dpdklab
2024-03-02  1:54 ` dpdklab
2024-03-02  1:55 ` dpdklab
2024-03-02  1:55 ` dpdklab
2024-03-02  1:55 ` dpdklab
2024-03-02  1:56 ` dpdklab
2024-03-02  1:56 ` dpdklab
2024-03-02  1:56 ` dpdklab
2024-03-02  1:56 ` dpdklab
2024-03-02  1:56 ` dpdklab
2024-03-02  1:57 ` dpdklab
2024-03-02  1:57 ` dpdklab
2024-03-02  1:57 ` dpdklab
2024-03-02  1:57 ` dpdklab
2024-03-02  1:58 ` dpdklab
2024-03-02  1:59 ` dpdklab
2024-03-02  2:00 ` dpdklab
2024-03-02  2:00 ` dpdklab
2024-03-02  2:03 ` dpdklab
2024-03-02  2:03 ` dpdklab
2024-03-02  2:03 ` dpdklab
2024-03-02  2:03 ` dpdklab
2024-03-02  2:03 ` dpdklab
2024-03-02  2:03 ` dpdklab
2024-03-02  2:04 ` dpdklab
2024-03-02  2:04 ` dpdklab
2024-03-02  2:06 ` dpdklab
2024-03-02  2:17 ` dpdklab
2024-03-02  2:17 ` dpdklab
2024-03-02  2:18 ` dpdklab
2024-03-02  2:18 ` dpdklab
2024-03-02  2:18 ` dpdklab
2024-03-02  2:19 ` dpdklab
2024-03-02  2:27 ` dpdklab
2024-03-02  2:28 ` dpdklab
2024-03-02  2:29 ` dpdklab
2024-03-02  2:36 ` dpdklab
2024-03-02  2:37 ` dpdklab
2024-03-02  2:38 ` dpdklab
2024-03-02  2:44 ` dpdklab
2024-03-02  2:45 ` dpdklab
2024-03-02  2:52 ` dpdklab
2024-03-02  3:00 ` dpdklab
2024-03-02  3:00 ` dpdklab
2024-03-02  4:42 ` dpdklab
2024-03-02  4:44 ` dpdklab
2024-03-03  2:54 ` dpdklab
2024-03-06  4:48 ` dpdklab
2024-03-06  5:35 ` dpdklab
2024-03-06  5:54 ` 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=65e26cc0.050a0220.a42a2.e37cSMTPIN_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).