From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136796 [PATCH] [v2] net/mlx5: enable PCI related counter
Date: Wed, 14 Feb 2024 13:01:16 -0800 (PST) [thread overview]
Message-ID: <65cd2a1c.050a0220.12e87.132bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136796
_Testing PASS_
Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Wednesday, February 14 2024 20:14:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:32bedd138f36b073341bbde2a5186727d1bc05d6
136796 --> testing pass
Test environment and result as below:
+--------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+======================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+--------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+--------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+--------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
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
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29152/
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-14 21:01 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 21:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 22:15 dpdklab
2024-02-14 21:59 dpdklab
2024-02-14 21:59 dpdklab
2024-02-14 21:58 dpdklab
2024-02-14 21:58 dpdklab
2024-02-14 21:57 dpdklab
2024-02-14 21:56 dpdklab
2024-02-14 21:55 dpdklab
2024-02-14 21:53 dpdklab
2024-02-14 21:53 dpdklab
2024-02-14 21:52 dpdklab
2024-02-14 21:50 dpdklab
2024-02-14 21:48 dpdklab
2024-02-14 21:40 dpdklab
2024-02-14 21:26 dpdklab
2024-02-14 21:25 dpdklab
2024-02-14 21:25 dpdklab
2024-02-14 21:25 dpdklab
2024-02-14 21:24 dpdklab
2024-02-14 21:23 dpdklab
2024-02-14 21:22 dpdklab
2024-02-14 21:22 dpdklab
2024-02-14 21:21 dpdklab
2024-02-14 21:21 dpdklab
2024-02-14 21:20 dpdklab
2024-02-14 21:20 dpdklab
2024-02-14 21:20 dpdklab
2024-02-14 21:20 dpdklab
2024-02-14 21:19 dpdklab
2024-02-14 21:16 dpdklab
2024-02-14 21:12 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:09 dpdklab
2024-02-14 21:07 dpdklab
2024-02-14 21:07 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:05 dpdklab
2024-02-14 21:05 dpdklab
2024-02-14 21:05 dpdklab
2024-02-14 21:05 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:03 dpdklab
2024-02-14 21:03 dpdklab
2024-02-14 21:03 dpdklab
2024-02-14 21:02 dpdklab
2024-02-14 21:02 dpdklab
2024-02-14 21:02 dpdklab
2024-02-14 21:02 dpdklab
2024-02-14 21:00 dpdklab
2024-02-14 20:59 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=65cd2a1c.050a0220.12e87.132bSMTPIN_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).