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 06:12:57 -0800 (PST) [thread overview]
Message-ID: <65b26c69.050a0220.bb554.49f2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-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 | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+==========================+==============================+===========================+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+
| Fedora 38 (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
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 14:13 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 14:12 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:22 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: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=65b26c69.050a0220.bb554.49f2SMTPIN_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).