From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137234-137237 [PATCH] [v3,4/4] common/qat: add gen5 devi
Date: Mon, 26 Feb 2024 09:53:46 -0800 (PST) [thread overview]
Message-ID: <65dcd02a.920a0220.48966.3241SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137237
_Testing PASS_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Monday, February 26 2024 17:08:18
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137234-137237 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29270/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-26 17:53 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 17:53 dpdklab [this message]
[not found] <20240226170818.533793-5-ciara.power@intel.com>
2024-02-28 2:33 ` dpdklab
2024-02-28 2:36 ` dpdklab
2024-02-28 2:38 ` dpdklab
2024-02-28 2:41 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 23:08 dpdklab
2024-02-26 23:00 dpdklab
2024-02-26 20:54 dpdklab
2024-02-26 20:25 dpdklab
2024-02-26 20:10 dpdklab
2024-02-26 19:34 dpdklab
2024-02-26 18:32 dpdklab
2024-02-26 18:32 dpdklab
2024-02-26 18:30 dpdklab
2024-02-26 18:24 dpdklab
2024-02-26 18:24 dpdklab
2024-02-26 18:23 dpdklab
2024-02-26 18:18 dpdklab
2024-02-26 18:10 dpdklab
2024-02-26 18:05 dpdklab
2024-02-26 18:04 dpdklab
2024-02-26 18:04 dpdklab
2024-02-26 18:04 dpdklab
2024-02-26 18:04 dpdklab
2024-02-26 18:03 dpdklab
2024-02-26 18:03 dpdklab
2024-02-26 18:02 dpdklab
2024-02-26 18:02 dpdklab
2024-02-26 18:02 dpdklab
2024-02-26 18:02 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:00 dpdklab
2024-02-26 18:00 dpdklab
2024-02-26 17:59 dpdklab
2024-02-26 17:59 dpdklab
2024-02-26 17:58 dpdklab
2024-02-26 17:58 dpdklab
2024-02-26 17:57 dpdklab
2024-02-26 17:57 dpdklab
2024-02-26 17:56 dpdklab
2024-02-26 17:56 dpdklab
2024-02-26 17:56 dpdklab
2024-02-26 17:56 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:54 dpdklab
2024-02-26 17:54 dpdklab
2024-02-26 17:54 dpdklab
2024-02-26 17:54 dpdklab
2024-02-26 17:53 dpdklab
2024-02-26 17:53 dpdklab
2024-02-26 17:53 dpdklab
2024-02-26 17:52 dpdklab
2024-02-26 17:52 dpdklab
2024-02-26 17:52 dpdklab
2024-02-26 17:51 dpdklab
2024-02-26 17:51 dpdklab
2024-02-26 17:51 dpdklab
2024-02-26 17:51 dpdklab
2024-02-26 17:50 dpdklab
2024-02-26 17:49 dpdklab
2024-02-26 17:49 dpdklab
2024-02-26 17:49 dpdklab
2024-02-26 17:49 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=65dcd02a.920a0220.48966.3241SMTPIN_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).