automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw141760 [PATCH v2] examples/fips_validation: fix coverity issues
Date: Wed, 26 Jun 2024 18:21:32 +0800	[thread overview]
Message-ID: <202406261021.45QALWsR3348916@localhost.localdomain> (raw)
In-Reply-To: <20240626102626.1934-1-gmuthukrishn@marvell.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/141760

_Compilation OK_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Wed, 26 Jun 2024 15:56:23 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 9ab7baa5c14b1ba928c09bda4734827d6d367d6b

141760 --> meson & ninja build successfully

Test environment and result as below:

+---------------------+----------------+
|     Environment     | compilation    |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS           |
+---------------------+----------------+

Loongnix-Server 8.3
    Kernel: 4.19.190+
    Compiler: gcc 8.3


       reply	other threads:[~2024-06-26 12:05 UTC|newest]

Thread overview: 135+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240626102626.1934-1-gmuthukrishn@marvell.com>
2024-06-26 10:21 ` qemudev [this message]
2024-06-26 10:26 ` qemudev
2024-06-26 10:48 ` |WARNING| " checkpatch
2024-06-26 11:45 ` |SUCCESS| " 0-day Robot
2024-06-26 13:09 ` |FAILURE| pw141760 [PATCH] [v2] examples/fips_validation: fix coveri dpdklab
2024-06-26 13:10 ` |SUCCESS| " dpdklab
2024-06-26 13:11 ` |FAILURE| " dpdklab
2024-06-26 13:17 ` |SUCCESS| " dpdklab
2024-06-26 13:18 ` |FAILURE| " dpdklab
2024-06-26 13:18 ` |SUCCESS| " dpdklab
2024-06-26 13:26 ` dpdklab
2024-06-26 13:32 ` dpdklab
2024-06-26 13:53 ` dpdklab
2024-06-26 13:56 ` dpdklab
2024-06-26 13:59 ` dpdklab
2024-06-26 14:04 ` dpdklab
2024-06-26 14:04 ` dpdklab
2024-06-26 14:04 ` dpdklab
2024-06-26 14:05 ` dpdklab
2024-06-26 14:05 ` dpdklab
2024-06-26 14:05 ` dpdklab
2024-06-26 14:06 ` dpdklab
2024-06-26 14:06 ` dpdklab
2024-06-26 14:06 ` dpdklab
2024-06-26 14:08 ` dpdklab
2024-06-26 14:09 ` dpdklab
2024-06-26 14:09 ` dpdklab
2024-06-26 14:10 ` dpdklab
2024-06-26 14:11 ` dpdklab
2024-06-26 14:17 ` dpdklab
2024-06-26 14:18 ` dpdklab
2024-06-26 14:18 ` dpdklab
2024-06-26 14:21 ` dpdklab
2024-06-26 14:21 ` dpdklab
2024-06-26 14:21 ` dpdklab
2024-06-26 14:22 ` dpdklab
2024-06-26 14:22 ` dpdklab
2024-06-26 14:24 ` dpdklab
2024-06-26 14:24 ` dpdklab
2024-06-26 14:24 ` dpdklab
2024-06-26 14:24 ` dpdklab
2024-06-26 14:25 ` dpdklab
2024-06-26 14:25 ` dpdklab
2024-06-26 14:26 ` dpdklab
2024-06-26 14:27 ` dpdklab
2024-06-26 14:27 ` dpdklab
2024-06-26 14:27 ` dpdklab
2024-06-26 14:30 ` dpdklab
2024-06-26 14:31 ` dpdklab
2024-06-26 14:32 ` dpdklab
2024-06-26 15:00 ` dpdklab
2024-06-26 15:05 ` dpdklab
2024-06-26 15:06 ` dpdklab
2024-06-26 15:07 ` dpdklab
2024-06-26 15:08 ` dpdklab
2024-06-26 15:08 ` dpdklab
2024-06-26 15:10 ` dpdklab
2024-06-26 15:12 ` dpdklab
2024-06-26 15:12 ` dpdklab
2024-06-26 15:26 ` dpdklab
2024-06-26 15:31 ` dpdklab
2024-06-26 15:33 ` dpdklab
2024-06-26 15:34 ` dpdklab
2024-06-26 15:35 ` dpdklab
2024-06-26 16:11 ` dpdklab
2024-06-26 16:11 ` dpdklab
2024-06-26 16:15 ` dpdklab
2024-06-26 16:16 ` dpdklab
2024-06-26 16:18 ` dpdklab
2024-06-26 16:20 ` dpdklab
2024-06-26 16:20 ` dpdklab
2024-06-26 16:22 ` dpdklab
2024-06-26 16:25 ` dpdklab
2024-06-26 16:28 ` dpdklab
2024-06-26 16:29 ` dpdklab
2024-06-26 16:30 ` dpdklab
2024-06-26 16:41 ` dpdklab
2024-06-26 16:42 ` dpdklab
2024-06-26 16:43 ` dpdklab
2024-06-26 16:44 ` dpdklab
2024-06-26 16:44 ` dpdklab
2024-06-26 16:45 ` dpdklab
2024-06-26 17:07 ` dpdklab
2024-06-26 17:09 ` dpdklab
2024-06-26 17:10 ` dpdklab
2024-06-26 17:19 ` dpdklab
2024-06-26 17:19 ` dpdklab
2024-06-26 17:20 ` dpdklab
2024-06-26 17:21 ` dpdklab
2024-06-26 17:21 ` dpdklab
2024-06-26 17:22 ` dpdklab
2024-06-26 17:22 ` dpdklab
2024-06-26 17:22 ` dpdklab
2024-06-26 17:23 ` dpdklab
2024-06-26 17:23 ` dpdklab
2024-06-26 17:24 ` dpdklab
2024-06-26 17:31 ` dpdklab
2024-06-26 17:31 ` dpdklab
2024-06-26 17:31 ` dpdklab
2024-06-26 17:32 ` dpdklab
2024-06-26 17:33 ` dpdklab
2024-06-26 17:33 ` dpdklab
2024-06-26 17:34 ` dpdklab
2024-06-26 17:34 ` dpdklab
2024-06-26 17:34 ` dpdklab
2024-06-26 17:35 ` dpdklab
2024-06-26 17:36 ` dpdklab
2024-06-26 17:36 ` dpdklab
2024-06-26 17:37 ` dpdklab
2024-06-26 17:39 ` dpdklab
2024-06-26 17:41 ` dpdklab
2024-06-26 17:48 ` dpdklab
2024-06-26 17:53 ` dpdklab
2024-06-26 19:03 ` dpdklab
2024-06-26 20:44 ` dpdklab
2024-06-27  3:15 ` dpdklab
2024-06-27  3:54 ` dpdklab
2024-06-27  9:09 ` dpdklab
2024-06-27  9:12 ` dpdklab
2024-06-27  9:12 ` dpdklab
2024-06-27  9:17 ` dpdklab
2024-06-27  9:20 ` dpdklab
2024-06-27  9:24 ` dpdklab
2024-06-27  9:30 ` dpdklab
2024-06-27  9:43 ` dpdklab
2024-06-27  9:45 ` dpdklab
2024-06-27 10:48 ` dpdklab
2024-06-27 10:53 ` dpdklab
2024-06-27 10:54 ` dpdklab
2024-06-27 10:58 ` dpdklab
2024-06-27 11:02 ` dpdklab
2024-06-27 11:22 ` dpdklab
2024-06-27 12:40 ` dpdklab
2024-06-27 12:49 ` dpdklab
2024-06-27 13:02 ` 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=202406261021.45QALWsR3348916@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --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).