From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: |SUCCESS| pw136579 [PATCH] net/mlx5: enable PCI related counters
Date: Sat, 10 Feb 2024 03:26:58 -0800 (PST) [thread overview]
Message-ID: <65c75d82.050a0220.50569.2bebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136579
_Testing PASS_
Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Friday, February 09 2024 20:41:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b9e20153ea808f12d89090655096c78b1918fc0e
136579 --> testing pass
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | PASS | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED | PASS |
+--------------+----------------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.15.0-91-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29109/
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-10 11:27 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 11:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-10 11:22 dpdklab
2024-02-10 10:58 dpdklab
2024-02-10 10:40 dpdklab
2024-02-10 10:39 dpdklab
2024-02-10 9:06 dpdklab
2024-02-10 8:53 dpdklab
2024-02-10 8:30 dpdklab
2024-02-10 8:28 dpdklab
2024-02-10 8:27 dpdklab
2024-02-10 8:24 dpdklab
2024-02-10 8:23 dpdklab
2024-02-10 8:20 dpdklab
2024-02-10 8:20 dpdklab
2024-02-10 8:18 dpdklab
2024-02-10 8:16 dpdklab
2024-02-10 8:15 dpdklab
2024-02-10 8:15 dpdklab
2024-02-10 8:14 dpdklab
2024-02-10 8:13 dpdklab
2024-02-10 8:12 dpdklab
2024-02-10 8:12 dpdklab
2024-02-10 8:11 dpdklab
2024-02-10 8:11 dpdklab
2024-02-10 8:11 dpdklab
2024-02-10 8:10 dpdklab
2024-02-10 8:10 dpdklab
2024-02-10 8:10 dpdklab
2024-02-10 8:10 dpdklab
2024-02-10 8:09 dpdklab
2024-02-10 8:09 dpdklab
2024-02-10 8:09 dpdklab
2024-02-10 8:08 dpdklab
2024-02-10 8:08 dpdklab
2024-02-10 8:08 dpdklab
2024-02-10 8:08 dpdklab
2024-02-10 8:08 dpdklab
2024-02-10 8:07 dpdklab
2024-02-10 8:06 dpdklab
2024-02-10 8:05 dpdklab
2024-02-10 8:05 dpdklab
2024-02-10 8:05 dpdklab
2024-02-10 8:03 dpdklab
2024-02-10 8:03 dpdklab
2024-02-10 8:03 dpdklab
2024-02-10 8:03 dpdklab
2024-02-10 7:59 dpdklab
2024-02-10 7:59 dpdklab
2024-02-10 7:58 dpdklab
2024-02-10 7:58 dpdklab
2024-02-10 7:58 dpdklab
2024-02-10 7:58 dpdklab
2024-02-10 7:58 dpdklab
2024-02-10 7:55 dpdklab
2024-02-10 7:55 dpdklab
2024-02-10 7:55 dpdklab
2024-02-10 7:55 dpdklab
2024-02-10 7:52 dpdklab
2024-02-10 7:51 dpdklab
2024-02-10 7:49 dpdklab
2024-02-10 7:48 dpdklab
2024-02-10 7:33 dpdklab
2024-02-10 7:32 dpdklab
2024-02-10 7:32 dpdklab
2024-02-10 7:31 dpdklab
2024-02-10 7:31 dpdklab
[not found] <20240209204142.1148790-1-wathsala.vithanage@arm.com>
2024-02-09 20:22 ` qemudev
2024-02-09 20:27 ` qemudev
2024-02-09 20:42 ` checkpatch
2024-02-09 21:44 ` 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=65c75d82.050a0220.50569.2bebSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@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).