From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw144625-144642 [PATCH] [v3,18/18] eal: add alloc_function
Date: Sun, 29 Sep 2024 14:38:07 -0700 (PDT) [thread overview]
Message-ID: <66f9c8bf.630a0220.93f6d.0934SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240929154107.62539-19-stephen@networkplumber.org>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/144642
_Testing pending_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sunday, September 29 2024 15:34:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:bf0ff8df59c7e32f95c0b542cc4a7918f8a3da84
144625-144642 --> testing pending
Upstream job id: Windows-Compile-DPDK-VS#3244
Test environment and result as below:
+---------------------+-------------------+-----------------------+----------------------+--------------------+
| Environment | dpdk_msvc_compile | dpdk_win_llvm_compile | dpdk_mingw64_compile | dpdk_meson_compile |
+=====================+===================+=======================+======================+====================+
| Windows Server 2022 | PASS | PEND | PEND | SKIPPED |
+---------------------+-------------------+-----------------------+----------------------+--------------------+
| FreeBSD 13.3 | SKIPPED | SKIPPED | SKIPPED | PEND |
+---------------------+-------------------+-----------------------+----------------------+--------------------+
| FreeBSD 14.1 | SKIPPED | SKIPPED | SKIPPED | PEND |
+---------------------+-------------------+-----------------------+----------------------+--------------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
FreeBSD 13.3
Kernel: 13.3-RELEASE-p5
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31175/
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-09-29 21:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240929154107.62539-19-stephen@networkplumber.org>
2024-09-29 15:17 ` |SUCCESS| pw144625-144642 [PATCH v3 18/18] eal: add alloc_function attribute to rte_malloc qemudev
2024-09-29 15:22 ` qemudev
2024-09-29 15:43 ` |SUCCESS| pw144642 " checkpatch
2024-09-29 16:44 ` 0-day Robot
2024-09-29 21:16 ` |SUCCESS| pw144625-144642 [PATCH] [v3,18/18] eal: add alloc_function dpdklab
2024-09-29 21:18 ` dpdklab
2024-09-29 21:25 ` dpdklab
2024-09-29 21:26 ` dpdklab
2024-09-29 21:30 ` dpdklab
2024-09-29 21:34 ` dpdklab
2024-09-29 21:38 ` dpdklab [this message]
2024-09-29 21:42 ` dpdklab
2024-09-29 21:47 ` dpdklab
2024-09-29 21:48 ` |PENDING| " dpdklab
2024-09-29 22:06 ` |SUCCESS| " dpdklab
2024-09-29 22:13 ` dpdklab
2024-09-29 22:21 ` |PENDING| " dpdklab
2024-09-29 22:23 ` |SUCCESS| " dpdklab
2024-09-29 22:55 ` dpdklab
2024-09-29 23:16 ` dpdklab
2024-09-29 23:16 ` dpdklab
2024-09-30 0:15 ` dpdklab
2024-09-30 2:41 ` 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=66f9c8bf.630a0220.93f6d.0934SMTPIN_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).