From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Weiguo Li <liwg06@foxmail.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133868 [PATCH] net/mlx5: fix the unlock mismatch issue
Date: Sat, 04 Nov 2023 03:15:20 -0700 (PDT) [thread overview]
Message-ID: <654619b8.4a0a0220.74911.e05cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133868
_Testing PASS_
Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Saturday, November 04 2023 04:07:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:34c0c38ab772e8eea5243f530866d5b68519e7c7
133868 --> testing pass
Test environment and result as below:
+--------------------------+----------------+---------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_zuc_autotest |
+==========================+================+===========================+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Debian 11 (arm) | SKIPPED | PASS |
+--------------------------+----------------+---------------------------+
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
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 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28240/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-04 10:15 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 10:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 12:47 dpdklab
2023-11-04 11:24 dpdklab
2023-11-04 11:04 dpdklab
2023-11-04 10:25 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:19 dpdklab
2023-11-04 10:16 dpdklab
2023-11-04 10:15 dpdklab
2023-11-04 10:14 dpdklab
2023-11-04 10:13 dpdklab
2023-11-04 10:13 dpdklab
2023-11-04 10:11 dpdklab
2023-11-04 10:11 dpdklab
2023-11-04 10:10 dpdklab
2023-11-04 10:10 dpdklab
2023-11-04 10:10 dpdklab
2023-11-04 10:10 dpdklab
2023-11-04 10:09 dpdklab
2023-11-04 10:09 dpdklab
2023-11-04 10:09 dpdklab
2023-11-04 10:09 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:05 dpdklab
2023-11-04 10:05 dpdklab
2023-11-04 10:04 dpdklab
2023-11-04 10:03 dpdklab
2023-11-04 9:54 dpdklab
2023-11-04 9:54 dpdklab
2023-11-04 9:44 dpdklab
2023-11-04 9:43 dpdklab
2023-11-04 9:43 dpdklab
2023-11-04 9:42 dpdklab
2023-11-04 9:17 dpdklab
[not found] <tencent_D1651EC7D3B588081DFD6FF1112691E61807@qq.com>
2023-11-04 3:54 ` qemudev
2023-11-04 3:58 ` qemudev
2023-11-04 5:19 ` 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=654619b8.4a0a0220.74911.e05cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=liwg06@foxmail.com \
--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).