From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136012-136013 [PATCH] [v3,2/2] event/cnxk: use WFE LDP l
Date: Sun, 21 Jan 2024 09:04:33 -0800 (PST) [thread overview]
Message-ID: <65ad4ea1.050a0220.e6806.b1c5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136013
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Sunday, January 21 2024 15:21:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1ba846683ee02b797c14854dc818c8ebad872071
136012-136013 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28924/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-21 17:04 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 17:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 22:32 dpdklab
2024-01-22 22:25 dpdklab
2024-01-21 19:10 dpdklab
2024-01-21 18:07 dpdklab
2024-01-21 17:52 dpdklab
2024-01-21 17:49 dpdklab
2024-01-21 17:40 dpdklab
2024-01-21 17:37 dpdklab
2024-01-21 17:36 dpdklab
2024-01-21 17:34 dpdklab
2024-01-21 17:33 dpdklab
2024-01-21 17:33 dpdklab
2024-01-21 17:32 dpdklab
2024-01-21 17:31 dpdklab
2024-01-21 17:30 dpdklab
2024-01-21 17:30 dpdklab
2024-01-21 17:29 dpdklab
2024-01-21 17:29 dpdklab
2024-01-21 17:29 dpdklab
2024-01-21 17:28 dpdklab
2024-01-21 17:27 dpdklab
2024-01-21 17:22 dpdklab
2024-01-21 17:14 dpdklab
2024-01-21 17:14 dpdklab
2024-01-21 17:03 dpdklab
2024-01-21 17:01 dpdklab
2024-01-21 17:01 dpdklab
2024-01-21 17:00 dpdklab
2024-01-21 16:57 dpdklab
2024-01-21 16:54 dpdklab
2024-01-21 16:53 dpdklab
2024-01-21 16:52 dpdklab
2024-01-21 16:52 dpdklab
2024-01-21 16:51 dpdklab
2024-01-21 16:50 dpdklab
2024-01-21 16:49 dpdklab
2024-01-21 16:48 dpdklab
2024-01-21 16:48 dpdklab
2024-01-21 16:47 dpdklab
2024-01-21 16:46 dpdklab
2024-01-21 16:43 dpdklab
2024-01-21 16:42 dpdklab
2024-01-21 16:41 dpdklab
2024-01-21 16:41 dpdklab
2024-01-21 16:41 dpdklab
2024-01-21 16:40 dpdklab
2024-01-21 16:40 dpdklab
2024-01-21 16:39 dpdklab
2024-01-21 16:36 dpdklab
2024-01-21 16:36 dpdklab
2024-01-21 16:34 dpdklab
2024-01-21 16:33 dpdklab
2024-01-21 16:33 dpdklab
2024-01-21 16:32 dpdklab
2024-01-21 16:30 dpdklab
2024-01-21 16:30 dpdklab
2024-01-21 16:30 dpdklab
2024-01-21 16:29 dpdklab
2024-01-21 16:28 dpdklab
2024-01-21 16:25 dpdklab
2024-01-21 16:23 dpdklab
2024-01-21 16:23 dpdklab
2024-01-21 16:22 dpdklab
2024-01-21 16:22 dpdklab
2024-01-21 16:22 dpdklab
2024-01-21 16:21 dpdklab
2024-01-21 16:21 dpdklab
2024-01-21 16:21 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=65ad4ea1.050a0220.e6806.b1c5SMTPIN_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).