From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw126884-126883 [PATCH] [v2, 3/3] net/mlx5: support enhanced multi-packet write on Windows
Date: Tue, 16 May 2023 06:43:41 -0700 (PDT) [thread overview]
Message-ID: <6463888d.d40a0220.77045.d2bdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-aarch64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126883
_Testing PASS_
Submitter: Tal Shnaiderman <talshn@nvidia.com>
Date: Tuesday, May 16 2023 11:25:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c
126884-126883 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM GCC Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
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/26239/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-16 13:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 13:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-16 22:23 dpdklab
2023-05-16 22:14 dpdklab
2023-05-16 22:09 dpdklab
2023-05-16 22:05 dpdklab
2023-05-16 21:50 dpdklab
2023-05-16 15:54 dpdklab
2023-05-16 15:54 dpdklab
2023-05-16 13:52 dpdklab
2023-05-16 13:51 dpdklab
2023-05-16 13:47 dpdklab
2023-05-16 13:46 dpdklab
2023-05-16 13:44 dpdklab
2023-05-16 13:42 dpdklab
2023-05-16 13:41 dpdklab
2023-05-16 13:39 dpdklab
2023-05-16 13:27 dpdklab
2023-05-16 13:26 dpdklab
2023-05-16 13:22 dpdklab
2023-05-16 13:06 dpdklab
2023-05-16 13:04 dpdklab
2023-05-16 13:02 dpdklab
2023-05-16 12:41 dpdklab
2023-05-16 12:37 dpdklab
2023-05-16 12:25 dpdklab
2023-05-16 12:24 dpdklab
2023-05-16 12:24 dpdklab
2023-05-16 12:22 dpdklab
2023-05-16 12:16 dpdklab
[not found] <20230516112548.6848-4-talshn@nvidia.com>
2023-05-16 11:17 ` |SUCCESS| pw126884-126883 [PATCH v2 " qemudev
2023-05-16 11:21 ` qemudev
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=6463888d.d40a0220.77045.d2bdSMTPIN_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).