From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138306 [PATCH] [v2] app/test: fix rsa tests in qat suite
Date: Wed, 13 Mar 2024 03:16:46 -0700 (PDT) [thread overview]
Message-ID: <65f17d0e.b00a0220.2a05a.76c7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240313091347.25207-1-arkadiuszx.kusztal@intel.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138306
_Testing PASS_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wednesday, March 13 2024 09:13:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a86f381b826660e88794754c41d3aec79ce9b87c
138306 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
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/29531/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-13 10:17 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240313091347.25207-1-arkadiuszx.kusztal@intel.com>
2024-03-13 8:51 ` |SUCCESS| pw138306 [PATCH v2] " qemudev
2024-03-13 8:55 ` qemudev
2024-03-13 9:14 ` checkpatch
2024-03-13 9:56 ` |SUCCESS| pw138306 [PATCH] [v2] " dpdklab
2024-03-13 9:57 ` |FAILURE| " dpdklab
2024-03-13 9:58 ` dpdklab
2024-03-13 9:58 ` |SUCCESS| " dpdklab
2024-03-13 9:59 ` dpdklab
2024-03-13 9:59 ` |FAILURE| " dpdklab
2024-03-13 10:07 ` |SUCCESS| " dpdklab
2024-03-13 10:07 ` |FAILURE| " dpdklab
2024-03-13 10:07 ` |SUCCESS| " dpdklab
2024-03-13 10:07 ` dpdklab
2024-03-13 10:08 ` dpdklab
2024-03-13 10:08 ` dpdklab
2024-03-13 10:08 ` dpdklab
2024-03-13 10:08 ` dpdklab
2024-03-13 10:09 ` dpdklab
2024-03-13 10:09 ` dpdklab
2024-03-13 10:09 ` dpdklab
2024-03-13 10:09 ` |FAILURE| " dpdklab
2024-03-13 10:09 ` |SUCCESS| " dpdklab
2024-03-13 10:09 ` |FAILURE| " dpdklab
2024-03-13 10:10 ` |SUCCESS| " dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` |FAILURE| " dpdklab
2024-03-13 10:10 ` |SUCCESS| " dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:11 ` |FAILURE| " dpdklab
2024-03-13 10:12 ` |SUCCESS| " dpdklab
2024-03-13 10:12 ` dpdklab
2024-03-13 10:13 ` dpdklab
2024-03-13 10:13 ` dpdklab
2024-03-13 10:13 ` dpdklab
2024-03-13 10:13 ` |FAILURE| " dpdklab
2024-03-13 10:13 ` |SUCCESS| " dpdklab
2024-03-13 10:13 ` dpdklab
2024-03-13 10:14 ` dpdklab
2024-03-13 10:14 ` |FAILURE| " dpdklab
2024-03-13 10:14 ` |SUCCESS| " dpdklab
2024-03-13 10:14 ` dpdklab
2024-03-13 10:14 ` dpdklab
2024-03-13 10:14 ` dpdklab
2024-03-13 10:15 ` dpdklab
2024-03-13 10:15 ` dpdklab
2024-03-13 10:15 ` dpdklab
2024-03-13 10:15 ` dpdklab
2024-03-13 10:16 ` |FAILURE| " dpdklab
2024-03-13 10:16 ` |SUCCESS| " dpdklab
2024-03-13 10:16 ` dpdklab
2024-03-13 10:16 ` dpdklab
2024-03-13 10:16 ` dpdklab
2024-03-13 10:16 ` dpdklab [this message]
2024-03-13 10:16 ` dpdklab
2024-03-13 10:17 ` |SUCCESS| pw138306 [PATCH v2] " 0-day Robot
2024-03-13 10:17 ` |SUCCESS| pw138306 [PATCH] [v2] " dpdklab
2024-03-13 10:17 ` dpdklab
2024-03-13 10:17 ` dpdklab
2024-03-13 10:17 ` dpdklab
2024-03-13 10:17 ` dpdklab
2024-03-13 10:18 ` dpdklab
2024-03-13 10:19 ` dpdklab
2024-03-13 10:19 ` dpdklab
2024-03-13 10:19 ` dpdklab
2024-03-13 10:19 ` dpdklab
2024-03-13 10:35 ` dpdklab
2024-03-13 10:35 ` |FAILURE| " dpdklab
2024-03-13 10:40 ` |SUCCESS| " dpdklab
2024-03-13 11:24 ` dpdklab
2024-03-16 22:57 ` dpdklab
2024-03-16 23:33 ` 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=65f17d0e.b00a0220.2a05a.76c7SMTPIN_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).