From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136131 [PATCH] vdpa/mlx5: fix queue enable drain CQ
Date: Thu, 25 Jan 2024 09:22:01 -0800 (PST) [thread overview]
Message-ID: <65b298b9.920a0220.75c8b.a1edSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136131
_Testing PASS_
Submitter: Yajun Wu <yajunw@nvidia.com>
Date: Thursday, January 25 2024 03:17:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:289ddcad152ebffa7359e414526707eb3f2c0a4a
136131 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
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 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28961/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-25 17:22 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 17:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 18:40 dpdklab
2024-01-26 18:26 dpdklab
2024-01-25 18:09 dpdklab
2024-01-25 17:51 dpdklab
2024-01-25 17:46 dpdklab
2024-01-25 17:28 dpdklab
2024-01-25 17:26 dpdklab
2024-01-25 17:20 dpdklab
2024-01-25 17:08 dpdklab
2024-01-25 17:07 dpdklab
2024-01-25 17:05 dpdklab
2024-01-25 16:59 dpdklab
2024-01-25 16:56 dpdklab
2024-01-25 16:51 dpdklab
2024-01-25 16:50 dpdklab
2024-01-25 16:43 dpdklab
2024-01-25 16:38 dpdklab
2024-01-25 16:32 dpdklab
2024-01-25 16:28 dpdklab
2024-01-25 16:27 dpdklab
2024-01-25 16:15 dpdklab
2024-01-25 16:14 dpdklab
2024-01-25 16:14 dpdklab
2024-01-25 16:00 dpdklab
2024-01-25 15:59 dpdklab
2024-01-25 15:58 dpdklab
2024-01-25 15:56 dpdklab
2024-01-25 15:56 dpdklab
2024-01-25 15:56 dpdklab
2024-01-25 15:55 dpdklab
2024-01-25 15:52 dpdklab
2024-01-25 15:51 dpdklab
2024-01-25 15:49 dpdklab
2024-01-25 15:48 dpdklab
2024-01-25 15:45 dpdklab
2024-01-25 15:44 dpdklab
2024-01-25 15:42 dpdklab
2024-01-25 15:42 dpdklab
2024-01-25 15:39 dpdklab
2024-01-25 15:39 dpdklab
2024-01-25 15:29 dpdklab
2024-01-25 15:28 dpdklab
2024-01-25 15:28 dpdklab
2024-01-25 15:19 dpdklab
2024-01-25 14:41 dpdklab
2024-01-25 14:35 dpdklab
2024-01-25 14:26 dpdklab
2024-01-25 14:19 dpdklab
2024-01-25 14:17 dpdklab
2024-01-25 14:17 dpdklab
2024-01-25 14:16 dpdklab
2024-01-25 14:12 dpdklab
2024-01-25 14:12 dpdklab
2024-01-25 14:11 dpdklab
2024-01-25 14:11 dpdklab
2024-01-25 14:10 dpdklab
2024-01-25 14:10 dpdklab
2024-01-25 14:10 dpdklab
2024-01-25 14:10 dpdklab
2024-01-25 14:09 dpdklab
2024-01-25 14:08 dpdklab
2024-01-25 14:06 dpdklab
2024-01-25 14:06 dpdklab
2024-01-25 13:55 dpdklab
[not found] <20240125031755.657102-1-yajunw@nvidia.com>
2024-01-25 2:55 ` qemudev
2024-01-25 3:00 ` qemudev
2024-01-25 3:20 ` checkpatch
2024-01-25 4:24 ` 0-day Robot
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=65b298b9.920a0220.75c8b.a1edSMTPIN_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).