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| pw141760 [PATCH] [v2] examples/fips_validation: fix coveri
Date: Wed, 26 Jun 2024 09:41:45 -0700 (PDT)	[thread overview]
Message-ID: <667c44c9.c80a0220.6c523.41faSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240626102626.1934-1-gmuthukrishn@marvell.com>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141760

_Testing PASS_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Wednesday, June 26 2024 10:26:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9ab7baa5c14b1ba928c09bda4734827d6d367d6b

141760 --> testing pass

Test environment and result as below:

+-------------------+----------------+
|    Environment    | dpdk_unit_test |
+===================+================+
| CentOS Stream 8   | PASS           |
+-------------------+----------------+
| Debian 12         | PASS           |
+-------------------+----------------+
| CentOS Stream 9   | PASS           |
+-------------------+----------------+
| Debian Bullseye   | PASS           |
+-------------------+----------------+
| Fedora 37         | PASS           |
+-------------------+----------------+
| Fedora 39         | PASS           |
+-------------------+----------------+
| Fedora 38         | PASS           |
+-------------------+----------------+
| RHEL9             | PASS           |
+-------------------+----------------+
| Fedora 38 (Clang) | PASS           |
+-------------------+----------------+
| Fedora 39 (Clang) | PASS           |
+-------------------+----------------+
| openSUSE Leap 15  | PASS           |
+-------------------+----------------+
| Fedora 40         | PASS           |
+-------------------+----------------+
| RHEL8             | PASS           |
+-------------------+----------------+
| Fedora 40 (Clang) | PASS           |
+-------------------+----------------+
| Ubuntu 24.04      | PASS           |
+-------------------+----------------+
| Ubuntu 22.04      | PASS           |
+-------------------+----------------+
| Ubuntu 20.04      | PASS           |
+-------------------+----------------+


CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-26 16:41 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 ` |SUCCESS| pw141760 [PATCH v2] examples/fips_validation: fix coverity issues qemudev
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 [this message]
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=667c44c9.c80a0220.6c523.41faSMTPIN_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).