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| pw139496 [PATCH] common/qat: add legacy algorithm option
Date: Thu, 18 Apr 2024 15:28:14 -0700 (PDT)	[thread overview]
Message-ID: <66219e7e.170a0220.d8fbc.53bbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240418165128.17261-1-arkadiuszx.kusztal@intel.com>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139496

_Testing PASS_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Thursday, April 18 2024 16:51:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139496 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK                   | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Fedora 39 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+


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

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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

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

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

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

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

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-18 22:28 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240418165128.17261-1-arkadiuszx.kusztal@intel.com>
2024-04-18 16:28 ` qemudev
2024-04-18 16:32 ` qemudev
2024-04-18 16:53 ` checkpatch
2024-04-18 17:44 ` 0-day Robot
2024-04-18 21:34 ` dpdklab
2024-04-18 21:37 ` dpdklab
2024-04-18 21:38 ` dpdklab
2024-04-18 21:39 ` dpdklab
2024-04-18 21:41 ` dpdklab
2024-04-18 22:13 ` dpdklab
2024-04-18 22:14 ` dpdklab
2024-04-18 22:14 ` dpdklab
2024-04-18 22:15 ` dpdklab
2024-04-18 22:15 ` dpdklab
2024-04-18 22:17 ` dpdklab
2024-04-18 22:18 ` dpdklab
2024-04-18 22:18 ` dpdklab
2024-04-18 22:18 ` dpdklab
2024-04-18 22:18 ` dpdklab
2024-04-18 22:18 ` dpdklab
2024-04-18 22:19 ` dpdklab
2024-04-18 22:19 ` dpdklab
2024-04-18 22:19 ` dpdklab
2024-04-18 22:20 ` dpdklab
2024-04-18 22:21 ` dpdklab
2024-04-18 22:21 ` dpdklab
2024-04-18 22:22 ` dpdklab
2024-04-18 22:22 ` dpdklab
2024-04-18 22:23 ` dpdklab
2024-04-18 22:23 ` dpdklab
2024-04-18 22:23 ` dpdklab
2024-04-18 22:24 ` dpdklab
2024-04-18 22:24 ` dpdklab
2024-04-18 22:24 ` dpdklab
2024-04-18 22:24 ` dpdklab
2024-04-18 22:25 ` dpdklab
2024-04-18 22:25 ` dpdklab
2024-04-18 22:25 ` dpdklab
2024-04-18 22:26 ` dpdklab
2024-04-18 22:26 ` dpdklab
2024-04-18 22:26 ` dpdklab
2024-04-18 22:27 ` dpdklab
2024-04-18 22:27 ` dpdklab
2024-04-18 22:27 ` dpdklab
2024-04-18 22:28 ` dpdklab
2024-04-18 22:28 ` dpdklab [this message]
2024-04-18 22:28 ` dpdklab
2024-04-18 22:28 ` dpdklab
2024-04-18 22:28 ` dpdklab
2024-04-18 22:28 ` dpdklab
2024-04-18 22:29 ` dpdklab
2024-04-18 22:29 ` dpdklab
2024-04-18 22:29 ` dpdklab
2024-04-18 22:29 ` dpdklab
2024-04-18 22:30 ` dpdklab
2024-04-18 22:30 ` dpdklab
2024-04-18 22:30 ` dpdklab
2024-04-18 22:30 ` dpdklab
2024-04-18 22:31 ` dpdklab
2024-04-18 22:31 ` dpdklab
2024-04-18 22:31 ` dpdklab
2024-04-18 22:32 ` dpdklab
2024-04-18 22:32 ` dpdklab
2024-04-18 22:32 ` dpdklab
2024-04-18 22:32 ` dpdklab
2024-04-18 22:32 ` dpdklab
2024-04-18 22:33 ` dpdklab
2024-04-18 22:33 ` dpdklab
2024-04-18 22:33 ` dpdklab
2024-04-18 22:34 ` dpdklab
2024-04-18 22:34 ` dpdklab
2024-04-18 22:34 ` dpdklab
2024-04-18 22:34 ` dpdklab
2024-04-18 22:37 ` dpdklab
2024-04-18 22:38 ` dpdklab
2024-04-18 22:38 ` dpdklab
2024-04-18 22:39 ` dpdklab
2024-04-18 22:39 ` dpdklab
2024-04-18 22:39 ` dpdklab
2024-04-18 22:39 ` dpdklab
2024-04-18 22:42 ` dpdklab
2024-04-18 22:42 ` dpdklab
2024-04-18 22:46 ` dpdklab
2024-04-18 22:46 ` dpdklab
2024-04-18 22:49 ` dpdklab
2024-04-18 22:56 ` dpdklab
2024-04-18 23:29 ` dpdklab
2024-04-19  0:21 ` dpdklab
2024-04-19  0:51 ` dpdklab
2024-04-19  0:57 ` 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=66219e7e.170a0220.d8fbc.53bbSMTPIN_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).