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| pw125146 [PATCH] [1/1] ml/cnxk: fix multiple coverity issues
Date: Wed, 15 Mar 2023 15:16:56 +0000 (UTC)	[thread overview]
Message-ID: <20230315151656.E34146011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125146

_Functional Testing PASS_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Wednesday, March 15 2023 13:54:27 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:baf13c3135d0c5998fff7edc23fb89412dc89246

125146 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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

UNH-IOL DPDK Community Lab

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

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

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 15:16 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-19  6:59 dpdklab
2023-03-19  6:59 dpdklab
2023-03-19  6:52 dpdklab
2023-03-19  6:51 dpdklab
2023-03-19  6:45 dpdklab
2023-03-19  6:43 dpdklab
2023-03-19  6:35 dpdklab
2023-03-19  6:31 dpdklab
2023-03-19  6:30 dpdklab
2023-03-19  6:29 dpdklab
2023-03-19  6:24 dpdklab
2023-03-19  6:15 dpdklab
2023-03-19  6:14 dpdklab
2023-03-19  6:11 dpdklab
2023-03-19  6:11 dpdklab
2023-03-19  6:09 dpdklab
2023-03-19  6:02 dpdklab
2023-03-19  5:57 dpdklab
2023-03-19  5:55 dpdklab
2023-03-19  5:54 dpdklab
2023-03-19  5:48 dpdklab
2023-03-19  5:41 dpdklab
2023-03-19  5:41 dpdklab
2023-03-19  5:38 dpdklab
2023-03-19  5:36 dpdklab
2023-03-19  5:35 dpdklab
2023-03-19  5:25 dpdklab
2023-03-19  4:51 dpdklab
2023-03-18  1:15 dpdklab
2023-03-18  0:25 dpdklab
2023-03-15 17:44 dpdklab
2023-03-15 17:42 dpdklab
2023-03-15 16:53 dpdklab
2023-03-15 16:43 dpdklab
2023-03-15 16:18 dpdklab
     [not found] <20230315135427.11489-1-syalavarthi@marvell.com>
2023-03-15 13:43 ` |SUCCESS| pw125146 [PATCH 1/1] " qemudev
2023-03-15 13:47 ` qemudev
2023-03-15 13:55 ` checkpatch
2023-03-15 15:59 ` 0-day Robot
2023-03-15 15:53 |SUCCESS| pw125146 [PATCH] [1/1] " dpdklab
2023-03-15 15:50 dpdklab
2023-03-15 15:47 dpdklab
2023-03-15 15:43 dpdklab
2023-03-15 15:41 dpdklab
2023-03-15 15:40 dpdklab
2023-03-15 15:35 dpdklab
2023-03-15 15:33 dpdklab
2023-03-15 15:28 dpdklab
2023-03-15 15:27 dpdklab
2023-03-15 15:24 dpdklab
2023-03-15 15:23 dpdklab
2023-03-15 15:20 dpdklab
2023-03-15 15:20 dpdklab
2023-03-15 15:18 dpdklab
2023-03-15 15:14 dpdklab
2023-03-15 15:13 dpdklab
2023-03-15 15:11 dpdklab
2023-03-15 15:09 dpdklab
2023-03-15 15:07 dpdklab
2023-03-15 15:06 dpdklab
2023-03-15 15:06 dpdklab
2023-03-15 14:56 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=20230315151656.E34146011D@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).