From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136930-136933 [PATCH] [v3,5/5] net/mlx5: validate the ac
Date: Tue, 20 Feb 2024 09:31:07 -0800 (PST) [thread overview]
Message-ID: <65d4e1db.170a0220.bcb50.49f6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136933
_Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Tuesday, February 20 2024 14:37:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ee45c93a16dd5e11b7779f18db9173fd8de8df74
136930-136933 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29197/
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-20 17:31 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 17:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 5:59 dpdklab
2024-02-21 5:56 dpdklab
2024-02-21 1:08 dpdklab
2024-02-21 0:49 dpdklab
2024-02-21 0:21 dpdklab
2024-02-20 19:55 dpdklab
2024-02-20 19:43 dpdklab
2024-02-20 19:17 dpdklab
2024-02-20 19:17 dpdklab
2024-02-20 19:14 dpdklab
2024-02-20 19:10 dpdklab
2024-02-20 19:04 dpdklab
2024-02-20 18:57 dpdklab
2024-02-20 18:49 dpdklab
2024-02-20 18:47 dpdklab
2024-02-20 18:01 dpdklab
2024-02-20 17:51 dpdklab
2024-02-20 17:48 dpdklab
2024-02-20 17:43 dpdklab
2024-02-20 17:37 dpdklab
2024-02-20 17:36 dpdklab
2024-02-20 17:35 dpdklab
2024-02-20 17:33 dpdklab
2024-02-20 17:30 dpdklab
2024-02-20 17:28 dpdklab
2024-02-20 17:27 dpdklab
2024-02-20 17:24 dpdklab
2024-02-20 17:23 dpdklab
2024-02-20 17:22 dpdklab
2024-02-20 17:22 dpdklab
2024-02-20 17:20 dpdklab
2024-02-20 17:20 dpdklab
2024-02-20 17:19 dpdklab
2024-02-20 17:18 dpdklab
2024-02-20 17:13 dpdklab
2024-02-20 17:12 dpdklab
2024-02-20 17:12 dpdklab
2024-02-20 17:10 dpdklab
2024-02-20 17:10 dpdklab
2024-02-20 17:09 dpdklab
2024-02-20 17:07 dpdklab
2024-02-20 17:02 dpdklab
2024-02-20 17:02 dpdklab
2024-02-20 17:01 dpdklab
2024-02-20 16:57 dpdklab
2024-02-20 16:46 dpdklab
2024-02-20 16:41 dpdklab
2024-02-20 16:39 dpdklab
2024-02-20 16:38 dpdklab
2024-02-20 16:37 dpdklab
2024-02-20 16:36 dpdklab
2024-02-20 16:35 dpdklab
2024-02-20 16:34 dpdklab
2024-02-20 16:32 dpdklab
2024-02-20 16:22 dpdklab
2024-02-20 16:16 dpdklab
2024-02-20 16:15 dpdklab
2024-02-20 16:12 dpdklab
2024-02-20 16:10 dpdklab
2024-02-20 16:10 dpdklab
2024-02-20 16:09 dpdklab
2024-02-20 16:09 dpdklab
2024-02-20 16:08 dpdklab
2024-02-20 16:05 dpdklab
2024-02-20 16:00 dpdklab
2024-02-20 15:59 dpdklab
2024-02-20 15:42 dpdklab
2024-02-20 15:42 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=65d4e1db.170a0220.bcb50.49f6SMTPIN_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).