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| pw137411 [PATCH] common/cnxk: fix Coverity issues
Date: Wed, 28 Feb 2024 03:41:04 -0800 (PST)	[thread overview]
Message-ID: <65df1bd0.050a0220.e36a4.b99dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228064643.1923169-1-psatheesh@marvell.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137411

_Testing PASS_

Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Wednesday, February 28 2024 06:46:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ab5b7cd5a0b563e6d49be6c8beaad1f39c581a5c

137411 --> testing pass

Test environment and result as below:

+--------------------------+------------------------------+----------------+--------------+---------------------------+
|       Environment        | cryptodev_sw_snow3g_autotest | dpdk_unit_test | lpm_autotest | cryptodev_sw_zuc_autotest |
+==========================+==============================+================+==============+===========================+
| Debian 12 (arm)          | PASS                         | PASS           | SKIPPED      | PASS                      |
+--------------------------+------------------------------+----------------+--------------+---------------------------+
| Debian 11 (Buster) (ARM) | SKIPPED                      | PASS           | SKIPPED      | SKIPPED                   |
+--------------------------+------------------------------+----------------+--------------+---------------------------+
| Fedora 37 (ARM)          | SKIPPED                      | PASS           | SKIPPED      | SKIPPED                   |
+--------------------------+------------------------------+----------------+--------------+---------------------------+
| Fedora 38 (ARM)          | SKIPPED                      | PASS           | SKIPPED      | SKIPPED                   |
+--------------------------+------------------------------+----------------+--------------+---------------------------+
| CentOS Stream 9 (ARM)    | SKIPPED                      | PASS           | SKIPPED      | SKIPPED                   |
+--------------------------+------------------------------+----------------+--------------+---------------------------+
| Ubuntu 20.04 (ARM)       | SKIPPED                      | PASS           | SKIPPED      | SKIPPED                   |
+--------------------------+------------------------------+----------------+--------------+---------------------------+
| Ubuntu 20.04 ARM SVE     | SKIPPED                      | SKIPPED        | PASS         | SKIPPED                   |
+--------------------------+------------------------------+----------------+--------------+---------------------------+


Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-28 11:41 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240228064643.1923169-1-psatheesh@marvell.com>
2024-02-28  6:25 ` qemudev
2024-02-28  6:29 ` qemudev
2024-02-28  6:48 ` checkpatch
2024-02-28  7:45 ` |SUCCESS| pw137411 [dpdk-dev] " 0-day Robot
2024-02-28 10:39 ` |SUCCESS| pw137411 " dpdklab
2024-02-28 10:53 ` dpdklab
2024-02-28 10:54 ` dpdklab
2024-02-28 10:54 ` dpdklab
2024-02-28 10:54 ` dpdklab
2024-02-28 10:54 ` dpdklab
2024-02-28 10:55 ` dpdklab
2024-02-28 10:55 ` dpdklab
2024-02-28 10:55 ` dpdklab
2024-02-28 10:55 ` dpdklab
2024-02-28 10:55 ` dpdklab
2024-02-28 10:56 ` dpdklab
2024-02-28 10:56 ` dpdklab
2024-02-28 10:56 ` dpdklab
2024-02-28 10:56 ` dpdklab
2024-02-28 10:56 ` dpdklab
2024-02-28 10:56 ` dpdklab
2024-02-28 10:57 ` dpdklab
2024-02-28 10:57 ` dpdklab
2024-02-28 10:58 ` dpdklab
2024-02-28 10:58 ` dpdklab
2024-02-28 11:04 ` dpdklab
2024-02-28 11:04 ` dpdklab
2024-02-28 11:04 ` dpdklab
2024-02-28 11:05 ` dpdklab
2024-02-28 11:05 ` dpdklab
2024-02-28 11:05 ` dpdklab
2024-02-28 11:05 ` dpdklab
2024-02-28 11:05 ` dpdklab
2024-02-28 11:05 ` dpdklab
2024-02-28 11:12 ` dpdklab
2024-02-28 11:12 ` dpdklab
2024-02-28 11:12 ` dpdklab
2024-02-28 11:12 ` dpdklab
2024-02-28 11:12 ` dpdklab
2024-02-28 11:13 ` dpdklab
2024-02-28 11:13 ` dpdklab
2024-02-28 11:13 ` dpdklab
2024-02-28 11:13 ` dpdklab
2024-02-28 11:14 ` dpdklab
2024-02-28 11:14 ` dpdklab
2024-02-28 11:15 ` dpdklab
2024-02-28 11:16 ` dpdklab
2024-02-28 11:17 ` dpdklab
2024-02-28 11:22 ` dpdklab
2024-02-28 11:22 ` dpdklab
2024-02-28 11:22 ` dpdklab
2024-02-28 11:23 ` dpdklab
2024-02-28 11:23 ` dpdklab
2024-02-28 11:23 ` dpdklab
2024-02-28 11:23 ` dpdklab
2024-02-28 11:23 ` dpdklab
2024-02-28 11:41 ` dpdklab [this message]
2024-02-28 11:44 ` dpdklab
2024-02-28 11:59 ` dpdklab
2024-02-28 12:00 ` dpdklab
2024-02-28 12:08 ` dpdklab
2024-02-28 13:03 ` dpdklab
2024-02-28 16:54 ` dpdklab
2024-02-28 17:55 ` dpdklab
2024-02-28 18:02 ` dpdklab
2024-02-29  7:18 ` dpdklab
2024-02-29 20:35 ` dpdklab
2024-02-29 20:42 ` dpdklab
2024-02-29 20:44 ` dpdklab
2024-02-29 20:48 ` dpdklab
2024-03-01  8:35 ` dpdklab
2024-03-01  9:09 ` dpdklab
2024-03-01  9:40 ` 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=65df1bd0.050a0220.e36a4.b99dSMTPIN_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).