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| pw138305 [PATCH] compress/nitrox: fix dereference after nu
Date: Wed, 13 Mar 2024 03:35:44 -0700 (PDT)	[thread overview]
Message-ID: <65f18180.b00a0220.ec4c5.02fcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240313060208.17791-1-rnagadheeraj@marvell.com>

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

_Functional Testing PASS_

Submitter: Nagadheeraj Rottela <rnagadheeraj@marvell.com>
Date: Wednesday, March 13 2024 06:02:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138305 --> 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/29530/

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-13 10:35 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240313060208.17791-1-rnagadheeraj@marvell.com>
2024-03-13  5:45 ` |SUCCESS| pw138305 [PATCH] compress/nitrox: fix dereference after null check qemudev
2024-03-13  5:50 ` qemudev
2024-03-13  6:04 ` checkpatch
2024-03-13  7:03 ` |FAILURE| " 0-day Robot
2024-03-13 10:19 ` |SUCCESS| pw138305 [PATCH] compress/nitrox: fix dereference after nu dpdklab
2024-03-13 10:19 ` dpdklab
2024-03-13 10:20 ` dpdklab
2024-03-13 10:23 ` dpdklab
2024-03-13 10:26 ` dpdklab
2024-03-13 10:35 ` dpdklab
2024-03-13 10:35 ` dpdklab
2024-03-13 10:35 ` dpdklab
2024-03-13 10:35 ` dpdklab [this message]
2024-03-13 10:36 ` dpdklab
2024-03-13 10:36 ` dpdklab
2024-03-13 10:36 ` dpdklab
2024-03-13 10:38 ` dpdklab
2024-03-13 10:38 ` dpdklab
2024-03-13 10:38 ` dpdklab
2024-03-13 10:39 ` dpdklab
2024-03-13 10:39 ` dpdklab
2024-03-13 10:39 ` dpdklab
2024-03-13 10:40 ` dpdklab
2024-03-13 10:40 ` dpdklab
2024-03-13 10:40 ` dpdklab
2024-03-13 10:40 ` dpdklab
2024-03-13 10:40 ` dpdklab
2024-03-13 10:40 ` dpdklab
2024-03-13 10:41 ` dpdklab
2024-03-13 10:41 ` dpdklab
2024-03-13 10:41 ` dpdklab
2024-03-13 10:41 ` dpdklab
2024-03-13 10:42 ` dpdklab
2024-03-13 10:42 ` dpdklab
2024-03-13 10:42 ` dpdklab
2024-03-13 10:42 ` dpdklab
2024-03-13 10:42 ` dpdklab
2024-03-13 10:42 ` dpdklab
2024-03-13 10:43 ` dpdklab
2024-03-13 10:43 ` dpdklab
2024-03-13 10:43 ` dpdklab
2024-03-13 10:43 ` dpdklab
2024-03-13 10:43 ` dpdklab
2024-03-13 10:44 ` dpdklab
2024-03-13 10:44 ` dpdklab
2024-03-13 10:44 ` dpdklab
2024-03-13 10:44 ` dpdklab
2024-03-13 10:44 ` dpdklab
2024-03-13 10:44 ` dpdklab
2024-03-13 10:45 ` dpdklab
2024-03-13 10:45 ` dpdklab
2024-03-13 10:45 ` dpdklab
2024-03-13 10:45 ` dpdklab
2024-03-13 10:45 ` dpdklab
2024-03-13 10:45 ` dpdklab
2024-03-13 10:46 ` dpdklab
2024-03-13 10:46 ` dpdklab
2024-03-13 10:46 ` dpdklab
2024-03-13 10:46 ` dpdklab
2024-03-13 10:46 ` dpdklab
2024-03-13 10:47 ` dpdklab
2024-03-13 10:47 ` dpdklab
2024-03-13 10:48 ` dpdklab
2024-03-13 10:49 ` dpdklab
2024-03-13 10:49 ` dpdklab
2024-03-13 10:50 ` dpdklab
2024-03-13 10:51 ` dpdklab
2024-03-13 10:51 ` dpdklab
2024-03-13 10:51 ` dpdklab
2024-03-13 10:56 ` dpdklab
2024-03-13 11:02 ` dpdklab
2024-03-13 11:03 ` dpdklab
2024-03-13 11:09 ` dpdklab
2024-03-13 11:10 ` dpdklab
2024-03-13 12:22 ` dpdklab
2024-03-17  0:13 ` dpdklab
2024-03-17  0:49 ` 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=65f18180.b00a0220.ec4c5.02fcSMTPIN_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).