From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130772 [PATCH] net/mlx5: fix jump ipool entry size
Date: Fri, 25 Aug 2023 17:58:42 -0700 (PDT) [thread overview]
Message-ID: <64e94e42.0d0a0220.6a938.ee3fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130772
_Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Friday, August 25 2023 18:43:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:934c0ccbfe881d861d749a9f8fb146d5f134c04c
130772 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27450/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-26 0:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 0:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-26 3:37 dpdklab
2023-08-26 3:19 dpdklab
2023-08-26 3:14 dpdklab
2023-08-26 3:09 dpdklab
2023-08-26 3:05 dpdklab
2023-08-26 2:54 dpdklab
2023-08-26 2:36 dpdklab
2023-08-26 1:52 dpdklab
2023-08-26 1:52 dpdklab
2023-08-26 1:37 dpdklab
2023-08-26 1:35 dpdklab
2023-08-26 1:28 dpdklab
2023-08-26 1:28 dpdklab
2023-08-26 1:27 dpdklab
2023-08-26 1:26 dpdklab
2023-08-26 1:24 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:19 dpdklab
2023-08-26 1:19 dpdklab
2023-08-26 1:19 dpdklab
2023-08-26 1:19 dpdklab
2023-08-26 1:18 dpdklab
2023-08-26 0:59 dpdklab
2023-08-26 0:58 dpdklab
2023-08-26 0:57 dpdklab
2023-08-26 0:50 dpdklab
2023-08-26 0:50 dpdklab
[not found] <20230825184330.3334318-1-dsosnowski@nvidia.com>
2023-08-25 18:40 ` qemudev
2023-08-25 18:44 ` qemudev
2023-08-25 18:44 ` checkpatch
2023-08-25 19:59 ` 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=64e94e42.0d0a0220.6a938.ee3fSMTPIN_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).