From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140185 [PATCH] net/mlx5: fix Rx Hash queue resource rele
Date: Mon, 20 May 2024 09:44:55 -0700 (PDT) [thread overview]
Message-ID: <664b7e07.920a0220.486fb.b684SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240520150709.39835-1-jiaweiw@nvidia.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140185
_Testing PASS_
Submitter: Jiawei Wang <jiaweiw@nvidia.com>
Date: Monday, May 20 2024 15:07:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7c0b8f196f0593ff2cb32a59332beea20a1ce5dc
140185 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | 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
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.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
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29979/
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-05-20 16:45 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240520150709.39835-1-jiaweiw@nvidia.com>
2024-05-20 14:41 ` |SUCCESS| pw140185 [PATCH] net/mlx5: fix Rx Hash queue resource release in sample flow qemudev
2024-05-20 14:46 ` qemudev
2024-05-20 15:08 ` checkpatch
2024-05-20 16:05 ` 0-day Robot
2024-05-20 16:23 ` |SUCCESS| pw140185 [PATCH] net/mlx5: fix Rx Hash queue resource rele dpdklab
2024-05-20 16:26 ` dpdklab
2024-05-20 16:35 ` dpdklab
2024-05-20 16:35 ` dpdklab
2024-05-20 16:35 ` dpdklab
2024-05-20 16:35 ` dpdklab
2024-05-20 16:36 ` dpdklab
2024-05-20 16:36 ` dpdklab
2024-05-20 16:36 ` dpdklab
2024-05-20 16:36 ` |FAILURE| " dpdklab
2024-05-20 16:36 ` dpdklab
2024-05-20 16:36 ` |SUCCESS| " dpdklab
2024-05-20 16:37 ` dpdklab
2024-05-20 16:37 ` dpdklab
2024-05-20 16:37 ` dpdklab
2024-05-20 16:37 ` dpdklab
2024-05-20 16:37 ` dpdklab
2024-05-20 16:37 ` dpdklab
2024-05-20 16:37 ` dpdklab
2024-05-20 16:37 ` |FAILURE| " dpdklab
2024-05-20 16:38 ` |SUCCESS| " dpdklab
2024-05-20 16:38 ` dpdklab
2024-05-20 16:38 ` dpdklab
2024-05-20 16:38 ` dpdklab
2024-05-20 16:38 ` dpdklab
2024-05-20 16:38 ` dpdklab
2024-05-20 16:38 ` |FAILURE| " dpdklab
2024-05-20 16:38 ` dpdklab
2024-05-20 16:38 ` |SUCCESS| " dpdklab
2024-05-20 16:39 ` dpdklab
2024-05-20 16:39 ` dpdklab
2024-05-20 16:39 ` dpdklab
2024-05-20 16:39 ` dpdklab
2024-05-20 16:39 ` dpdklab
2024-05-20 16:39 ` dpdklab
2024-05-20 16:40 ` |FAILURE| " dpdklab
2024-05-20 16:40 ` |SUCCESS| " dpdklab
2024-05-20 16:40 ` |FAILURE| " dpdklab
2024-05-20 16:40 ` |SUCCESS| " dpdklab
2024-05-20 16:40 ` |FAILURE| " dpdklab
2024-05-20 16:40 ` |SUCCESS| " dpdklab
2024-05-20 16:40 ` dpdklab
2024-05-20 16:41 ` dpdklab
2024-05-20 16:41 ` dpdklab
2024-05-20 16:41 ` dpdklab
2024-05-20 16:41 ` dpdklab
2024-05-20 16:41 ` dpdklab
2024-05-20 16:41 ` dpdklab
2024-05-20 16:41 ` dpdklab
2024-05-20 16:42 ` dpdklab
2024-05-20 16:42 ` dpdklab
2024-05-20 16:42 ` |FAILURE| " dpdklab
2024-05-20 16:42 ` dpdklab
2024-05-20 16:42 ` |SUCCESS| " dpdklab
2024-05-20 16:43 ` |FAILURE| " dpdklab
2024-05-20 16:44 ` |SUCCESS| " dpdklab
2024-05-20 16:44 ` dpdklab
2024-05-20 16:44 ` dpdklab
2024-05-20 16:44 ` dpdklab
2024-05-20 16:44 ` dpdklab [this message]
2024-05-20 16:45 ` dpdklab
2024-05-20 16:45 ` dpdklab
2024-05-20 16:45 ` dpdklab
2024-05-20 16:45 ` dpdklab
2024-05-20 16:46 ` dpdklab
2024-05-20 16:46 ` |FAILURE| " dpdklab
2024-05-20 16:46 ` |SUCCESS| " dpdklab
2024-05-20 16:47 ` dpdklab
2024-05-20 16:47 ` dpdklab
2024-05-20 16:48 ` |FAILURE| " dpdklab
2024-05-20 16:48 ` |SUCCESS| " dpdklab
2024-05-20 16:48 ` |FAILURE| " dpdklab
2024-05-20 16:49 ` |SUCCESS| " dpdklab
2024-05-20 16:50 ` |FAILURE| " dpdklab
2024-05-20 16:51 ` dpdklab
2024-05-20 16:52 ` |SUCCESS| " dpdklab
2024-05-20 16:52 ` |FAILURE| " dpdklab
2024-05-20 16:52 ` |SUCCESS| " dpdklab
2024-05-20 17:31 ` |FAILURE| " dpdklab
2024-05-20 17:32 ` dpdklab
2024-05-20 17:37 ` |SUCCESS| " dpdklab
2024-05-20 17:40 ` dpdklab
2024-05-20 17:42 ` dpdklab
2024-05-20 17:50 ` dpdklab
2024-05-23 6:18 ` 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=664b7e07.920a0220.486fb.b684SMTPIN_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).