From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw122304 [PATCH] [v2] crypto/qat: fix build
Date: Thu, 19 Jan 2023 03:14:21 +0000 (UTC) [thread overview]
Message-ID: <20230119031421.CEB86601CE@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4921 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/122304
_Testing PASS_
Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Wednesday, January 18 2023 11:05:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:83397b9f073904438965e1fda2efe76f7850fe01
122304 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+----------------------+----------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_unit_test |
+========================================+====================+======================+================+
| FreeBSD 13 | PASS | SKIPPED | SKIPPED |
+----------------------------------------+--------------------+----------------------+----------------+
| Windows Server 2019 | PASS | PASS | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 ARM GCC Native | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 ARM Clang Native | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| RHEL 7 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| openSUSE Leap 15 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Debian Buster | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Debian Bullseye | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 22.04 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| CentOS Stream 9 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS | SKIPPED | SKIPPED |
+----------------------------------------+--------------------+----------------------+----------------+
| CentOS Stream 8 | SKIPPED | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| RHEL8 | SKIPPED | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25026/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-01-19 3:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 3:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-21 2:31 dpdklab
2023-01-19 4:44 dpdklab
2023-01-19 3:14 dpdklab
2023-01-19 3:14 dpdklab
2023-01-19 3:14 dpdklab
2023-01-19 3:14 dpdklab
2023-01-19 3:13 dpdklab
2023-01-19 3:13 dpdklab
2023-01-18 12:03 dpdklab
2023-01-18 12:00 dpdklab
[not found] <20230118110558.1136485-1-pablo.de.lara.guarch@intel.com>
2023-01-18 10:58 ` |SUCCESS| pw122304 [PATCH v2] " qemudev
2023-01-18 11:02 ` qemudev
2023-01-18 11:06 ` checkpatch
2023-01-18 11:59 ` 0-day Robot
2023-01-18 11:51 |SUCCESS| pw122304 [PATCH] [v2] " dpdklab
2023-01-18 11:44 dpdklab
2023-01-18 11:43 dpdklab
2023-01-18 11:41 dpdklab
2023-01-18 11:41 dpdklab
2023-01-18 11:37 dpdklab
2023-01-18 11:35 dpdklab
2023-01-18 11:34 dpdklab
2023-01-18 11:34 dpdklab
2023-01-18 11:31 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=20230119031421.CEB86601CE@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).