From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136749 [PATCH] eal: add helper to skip whitespaces
Date: Wed, 14 Feb 2024 04:53:46 -0800 (PST) [thread overview]
Message-ID: <65ccb7da.050a0220.a46f6.265bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136749
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Wednesday, February 14 2024 12:12:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31d72ff4dc7c057366153e9918ac92bf9123a3bc
136749 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29147/
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-14 12:53 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 12:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 18:27 dpdklab
2024-02-14 17:53 dpdklab
2024-02-14 16:43 dpdklab
2024-02-14 16:24 dpdklab
2024-02-14 15:56 dpdklab
2024-02-14 14:41 dpdklab
2024-02-14 14:39 dpdklab
2024-02-14 14:34 dpdklab
2024-02-14 14:27 dpdklab
2024-02-14 14:23 dpdklab
2024-02-14 14:20 dpdklab
2024-02-14 14:13 dpdklab
2024-02-14 14:09 dpdklab
2024-02-14 14:02 dpdklab
2024-02-14 13:55 dpdklab
2024-02-14 13:49 dpdklab
2024-02-14 13:48 dpdklab
2024-02-14 13:47 dpdklab
2024-02-14 13:45 dpdklab
2024-02-14 13:44 dpdklab
2024-02-14 13:41 dpdklab
2024-02-14 13:40 dpdklab
2024-02-14 13:37 dpdklab
2024-02-14 13:35 dpdklab
2024-02-14 13:34 dpdklab
2024-02-14 13:33 dpdklab
2024-02-14 13:33 dpdklab
2024-02-14 13:32 dpdklab
2024-02-14 13:32 dpdklab
2024-02-14 13:31 dpdklab
2024-02-14 13:31 dpdklab
2024-02-14 13:27 dpdklab
2024-02-14 13:26 dpdklab
2024-02-14 13:25 dpdklab
2024-02-14 13:25 dpdklab
2024-02-14 13:24 dpdklab
2024-02-14 13:24 dpdklab
2024-02-14 13:23 dpdklab
2024-02-14 13:23 dpdklab
2024-02-14 13:22 dpdklab
2024-02-14 13:21 dpdklab
2024-02-14 13:21 dpdklab
2024-02-14 13:12 dpdklab
2024-02-14 13:12 dpdklab
2024-02-14 13:11 dpdklab
2024-02-14 13:11 dpdklab
2024-02-14 13:11 dpdklab
2024-02-14 13:11 dpdklab
2024-02-14 13:05 dpdklab
2024-02-14 13:05 dpdklab
2024-02-14 13:05 dpdklab
2024-02-14 13:05 dpdklab
2024-02-14 13:03 dpdklab
2024-02-14 13:03 dpdklab
2024-02-14 13:02 dpdklab
2024-02-14 13:02 dpdklab
2024-02-14 13:01 dpdklab
2024-02-14 13:01 dpdklab
2024-02-14 13:00 dpdklab
2024-02-14 13:00 dpdklab
2024-02-14 12:59 dpdklab
2024-02-14 12:56 dpdklab
2024-02-14 12:55 dpdklab
2024-02-14 12:54 dpdklab
2024-02-14 12:54 dpdklab
2024-02-14 12:54 dpdklab
2024-02-14 12:54 dpdklab
2024-02-14 12:53 dpdklab
2024-02-14 12:53 dpdklab
[not found] <20240214121219.3408867-1-david.marchand@redhat.com>
2024-02-14 11:50 ` qemudev
2024-02-14 11:54 ` qemudev
2024-02-14 12:14 ` checkpatch
2024-02-14 13:04 ` 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=65ccb7da.050a0220.a46f6.265bSMTPIN_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).