From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136835 [PATCH] [v3] net/mlx5: enable PCI related counter
Date: Thu, 15 Feb 2024 13:48:01 -0800 (PST) [thread overview]
Message-ID: <65ce8691.050a0220.99f40.4ee5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136835
_Testing PASS_
Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Thursday, February 15 2024 18:26:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:25e981ab82d28bdc6010f033efc2fdcc35fc2b53
136835 --> testing pass
Test environment and result as below:
+--------------------------+----------------+--------------+
| Environment | dpdk_unit_test | lpm_autotest |
+==========================+================+==============+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS |
+--------------------------+----------------+--------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.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/29163/
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-15 21:48 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 21:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 23:20 dpdklab
2024-02-15 23:16 dpdklab
2024-02-15 23:04 dpdklab
2024-02-15 23:01 dpdklab
2024-02-15 23:00 dpdklab
2024-02-15 22:50 dpdklab
2024-02-15 22:45 dpdklab
2024-02-15 22:42 dpdklab
2024-02-15 22:41 dpdklab
2024-02-15 22:40 dpdklab
2024-02-15 22:38 dpdklab
2024-02-15 22:37 dpdklab
2024-02-15 22:36 dpdklab
2024-02-15 22:35 dpdklab
2024-02-15 22:35 dpdklab
2024-02-15 22:32 dpdklab
2024-02-15 22:31 dpdklab
2024-02-15 22:30 dpdklab
2024-02-15 22:29 dpdklab
2024-02-15 22:23 dpdklab
2024-02-15 22:20 dpdklab
2024-02-15 22:19 dpdklab
2024-02-15 22:18 dpdklab
2024-02-15 22:13 dpdklab
2024-02-15 22:13 dpdklab
2024-02-15 22:09 dpdklab
2024-02-15 22:08 dpdklab
2024-02-15 22:07 dpdklab
2024-02-15 22:07 dpdklab
2024-02-15 22:05 dpdklab
2024-02-15 22:02 dpdklab
2024-02-15 22:02 dpdklab
2024-02-15 21:56 dpdklab
2024-02-15 21:56 dpdklab
2024-02-15 21:54 dpdklab
2024-02-15 21:52 dpdklab
2024-02-15 21:51 dpdklab
2024-02-15 21:46 dpdklab
2024-02-15 21:45 dpdklab
2024-02-15 21:44 dpdklab
2024-02-15 21:44 dpdklab
2024-02-15 21:42 dpdklab
2024-02-15 21:41 dpdklab
2024-02-15 21:36 dpdklab
2024-02-15 21:34 dpdklab
2024-02-15 21:34 dpdklab
2024-02-15 21:33 dpdklab
2024-02-15 21:29 dpdklab
2024-02-15 21:27 dpdklab
2024-02-15 21:20 dpdklab
2024-02-15 21:19 dpdklab
2024-02-15 21:18 dpdklab
2024-02-15 21:17 dpdklab
2024-02-15 21:16 dpdklab
2024-02-15 21:15 dpdklab
2024-02-15 21:15 dpdklab
2024-02-15 21:11 dpdklab
2024-02-15 21:08 dpdklab
2024-02-15 21:08 dpdklab
2024-02-15 21:06 dpdklab
2024-02-15 21:05 dpdklab
2024-02-15 21:05 dpdklab
2024-02-15 21:05 dpdklab
2024-02-15 21:04 dpdklab
2024-02-15 21:04 dpdklab
2024-02-15 21:03 dpdklab
2024-02-15 21:03 dpdklab
2024-02-15 21:02 dpdklab
2024-02-15 20:59 dpdklab
2024-02-15 20:54 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=65ce8691.050a0220.99f40.4ee5SMTPIN_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).