From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw141965 [PATCH] [v2] devtools: check that maintainers are
Date: Fri, 28 Jun 2024 08:39:36 -0700 (PDT) [thread overview]
Message-ID: <667ed938.c80a0220.6b38b.3e65SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240628125612.3049232-1-david.marchand@redhat.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/141965
_Testing pending_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, June 28 2024 12:56:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b
141965 --> testing pending
Test environment and result as below:
+---------------------+----------------------+-------------------+--------------------+
| Environment | dpdk_mingw64_compile | dpdk_msvc_compile | dpdk_meson_compile |
+=====================+======================+===================+====================+
| Windows Server 2019 | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+-------------------+--------------------+
| Windows Server 2022 | PEND | PEND | SKIPPED |
+---------------------+----------------------+-------------------+--------------------+
| FreeBSD 13.3 | SKIPPED | SKIPPED | PASS |
+---------------------+----------------------+-------------------+--------------------+
| FreeBSD 14.1 | SKIPPED | SKIPPED | PEND |
+---------------------+----------------------+-------------------+--------------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30347/
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-06-28 15:39 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240628125612.3049232-1-david.marchand@redhat.com>
2024-06-28 12:29 ` |SUCCESS| pw141965 [PATCH v2] devtools: check that maintainers are listed in mailmap qemudev
2024-06-28 12:34 ` qemudev
2024-06-28 12:57 ` checkpatch
2024-06-28 13:45 ` 0-day Robot
2024-06-28 15:26 ` |SUCCESS| pw141965 [PATCH] [v2] devtools: check that maintainers are dpdklab
2024-06-28 15:28 ` dpdklab
2024-06-28 15:29 ` dpdklab
2024-06-28 15:31 ` dpdklab
2024-06-28 15:32 ` dpdklab
2024-06-28 15:34 ` dpdklab
2024-06-28 15:36 ` dpdklab
2024-06-28 15:36 ` dpdklab
2024-06-28 15:37 ` dpdklab
2024-06-28 15:38 ` |PENDING| " dpdklab
2024-06-28 15:39 ` dpdklab [this message]
2024-06-28 15:41 ` |SUCCESS| " dpdklab
2024-06-28 15:44 ` dpdklab
2024-06-28 15:45 ` |PENDING| " dpdklab
2024-06-28 15:48 ` dpdklab
2024-06-28 15:48 ` |SUCCESS| " dpdklab
2024-06-28 15:49 ` dpdklab
2024-06-28 15:51 ` |PENDING| " dpdklab
2024-06-28 15:52 ` dpdklab
2024-06-28 15:53 ` |SUCCESS| " dpdklab
2024-06-28 16:44 ` |PENDING| " dpdklab
2024-06-28 16:44 ` dpdklab
2024-06-28 16:44 ` dpdklab
2024-06-28 16:45 ` dpdklab
2024-06-28 16:45 ` |SUCCESS| " dpdklab
2024-06-28 16:45 ` |PENDING| " dpdklab
2024-06-28 16:45 ` dpdklab
2024-06-28 16:45 ` dpdklab
2024-06-28 16:46 ` dpdklab
2024-06-28 16:47 ` dpdklab
2024-06-28 16:48 ` dpdklab
2024-06-28 16:55 ` dpdklab
2024-06-28 16:56 ` dpdklab
2024-06-28 16:57 ` dpdklab
2024-06-28 17:03 ` dpdklab
2024-06-28 17:07 ` dpdklab
2024-06-28 17:08 ` dpdklab
2024-06-28 17:11 ` dpdklab
2024-06-28 17:25 ` dpdklab
2024-06-28 17:25 ` dpdklab
2024-06-28 17:26 ` dpdklab
2024-06-28 17:27 ` dpdklab
2024-06-28 17:30 ` dpdklab
2024-06-28 17:34 ` dpdklab
2024-06-28 17:34 ` dpdklab
2024-06-28 17:40 ` dpdklab
2024-06-28 17:40 ` dpdklab
2024-06-28 17:44 ` dpdklab
2024-06-28 17:46 ` dpdklab
2024-06-28 17:48 ` dpdklab
2024-06-28 17:50 ` |SUCCESS| " dpdklab
2024-06-28 17:51 ` dpdklab
2024-06-28 18:36 ` |PENDING| " dpdklab
2024-06-28 19:08 ` |SUCCESS| " dpdklab
2024-06-28 19:19 ` dpdklab
2024-06-28 22:40 ` |PENDING| " dpdklab
2024-06-28 22:41 ` dpdklab
2024-06-28 22:43 ` |SUCCESS| " dpdklab
2024-06-28 22:43 ` |PENDING| " dpdklab
2024-06-28 22:45 ` dpdklab
2024-06-28 22:50 ` dpdklab
2024-06-28 22:51 ` dpdklab
2024-06-28 22:53 ` dpdklab
2024-06-28 22:54 ` dpdklab
2024-06-28 22:54 ` dpdklab
2024-06-28 22:55 ` dpdklab
2024-06-28 22:57 ` dpdklab
2024-06-28 22:57 ` dpdklab
2024-06-28 22:59 ` dpdklab
2024-06-28 22:59 ` dpdklab
2024-06-28 23:00 ` dpdklab
2024-06-28 23:00 ` dpdklab
2024-06-28 23:02 ` dpdklab
2024-06-28 23:02 ` dpdklab
2024-06-28 23:02 ` dpdklab
2024-06-28 23:02 ` dpdklab
2024-06-28 23:03 ` dpdklab
2024-06-28 23:03 ` dpdklab
2024-06-28 23:04 ` dpdklab
2024-06-28 23:04 ` dpdklab
2024-06-28 23:05 ` dpdklab
2024-06-28 23:07 ` dpdklab
2024-06-28 23:09 ` dpdklab
2024-06-28 23:09 ` dpdklab
2024-06-28 23:09 ` dpdklab
2024-06-28 23:09 ` dpdklab
2024-06-28 23:10 ` dpdklab
2024-06-28 23:13 ` dpdklab
2024-06-28 23:13 ` dpdklab
2024-06-28 23:15 ` dpdklab
2024-06-28 23:17 ` dpdklab
2024-06-28 23:20 ` dpdklab
2024-06-28 23:25 ` dpdklab
2024-06-28 23:28 ` dpdklab
2024-06-28 23:28 ` dpdklab
2024-06-28 23:32 ` dpdklab
2024-06-28 23:35 ` dpdklab
2024-06-28 23:35 ` dpdklab
2024-06-28 23:36 ` dpdklab
2024-06-28 23:36 ` |SUCCESS| " dpdklab
2024-06-28 23:37 ` |PENDING| " dpdklab
2024-06-28 23:42 ` |SUCCESS| " dpdklab
2024-06-28 23:49 ` dpdklab
2024-06-28 23:58 ` |PENDING| " dpdklab
2024-06-29 0:01 ` |SUCCESS| " dpdklab
2024-06-29 0:23 ` |PENDING| " dpdklab
2024-06-29 0:26 ` |SUCCESS| " dpdklab
2024-06-29 1:13 ` dpdklab
2024-06-29 1:26 ` dpdklab
2024-06-29 11:53 ` dpdklab
2024-07-01 14:45 ` 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=667ed938.c80a0220.6b38b.3e65SMTPIN_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).