From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137457 [PATCH] net/mlx5: fix counter cache starvation
Date: Wed, 28 Feb 2024 18:04:43 -0800 (PST) [thread overview]
Message-ID: <65dfe63b.050a0220.53fad.0365SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228190607.187958-1-dsosnowski@nvidia.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137457
_Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, February 28 2024 19:06:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:513a698fe1ddcb725d0ed6bca2cbc4b6fc7c8345
137457 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian 12 (arm) | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29323/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-02-29 2:04 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228190607.187958-1-dsosnowski@nvidia.com>
2024-02-28 18:44 ` qemudev
2024-02-28 18:48 ` qemudev
2024-02-28 19:08 ` checkpatch
2024-02-28 20:05 ` 0-day Robot
2024-02-29 1:44 ` dpdklab
2024-02-29 1:49 ` dpdklab
2024-02-29 1:50 ` dpdklab
2024-02-29 1:51 ` dpdklab
2024-02-29 1:51 ` dpdklab
2024-02-29 1:52 ` dpdklab
2024-02-29 1:53 ` dpdklab
2024-02-29 1:54 ` dpdklab
2024-02-29 1:54 ` dpdklab
2024-02-29 1:54 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:56 ` dpdklab
2024-02-29 1:58 ` dpdklab
2024-02-29 1:58 ` dpdklab
2024-02-29 1:59 ` dpdklab
2024-02-29 1:59 ` dpdklab
2024-02-29 1:59 ` dpdklab
2024-02-29 1:59 ` dpdklab
2024-02-29 2:00 ` dpdklab
2024-02-29 2:00 ` dpdklab
2024-02-29 2:01 ` dpdklab
2024-02-29 2:01 ` dpdklab
2024-02-29 2:01 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:03 ` dpdklab
2024-02-29 2:03 ` dpdklab
2024-02-29 2:04 ` dpdklab
2024-02-29 2:04 ` dpdklab
2024-02-29 2:04 ` dpdklab [this message]
2024-02-29 2:04 ` dpdklab
2024-02-29 2:04 ` dpdklab
2024-02-29 2:05 ` dpdklab
2024-02-29 2:05 ` dpdklab
2024-02-29 2:05 ` dpdklab
2024-02-29 2:05 ` dpdklab
2024-02-29 2:06 ` dpdklab
2024-02-29 2:06 ` dpdklab
2024-02-29 2:11 ` dpdklab
2024-02-29 2:15 ` dpdklab
2024-02-29 2:15 ` dpdklab
2024-02-29 2:15 ` dpdklab
2024-02-29 2:18 ` dpdklab
2024-02-29 2:19 ` dpdklab
2024-02-29 2:19 ` dpdklab
2024-02-29 2:20 ` dpdklab
2024-02-29 2:20 ` dpdklab
2024-02-29 2:20 ` dpdklab
2024-02-29 2:21 ` dpdklab
2024-02-29 2:22 ` dpdklab
2024-02-29 2:22 ` dpdklab
2024-02-29 2:22 ` dpdklab
2024-02-29 2:24 ` dpdklab
2024-02-29 2:24 ` dpdklab
2024-02-29 3:05 ` dpdklab
2024-03-01 1:51 ` dpdklab
2024-03-01 1:57 ` dpdklab
2024-03-01 2:08 ` dpdklab
2024-03-01 2:08 ` dpdklab
2024-03-01 16:50 ` |WARNING| " dpdklab
2024-03-02 8:35 ` |SUCCESS| " dpdklab
2024-03-02 9:08 ` dpdklab
2024-03-02 9:40 ` |WARNING| " dpdklab
2024-03-02 21:50 ` |SUCCESS| " 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=65dfe63b.050a0220.53fad.0365SMTPIN_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).