From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw145753-145756 [PATCH] [v14,4/4] eal: add PMU support to
Date: Fri, 11 Oct 2024 15:13:00 -0700 (PDT) [thread overview]
Message-ID: <6709a2ec.050a0220.fa6c2.a3b5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241011094944.3586051-5-tduszynski@marvell.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/145756
_Testing pending_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Friday, October 11 2024 09:49:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:98613d32e3dac58d685f4f236cf8cc9733abaaf3
145753-145756 --> testing pending
Upstream job id: Generic-VM-DPDK-Compile-Meson#30199
Test environment and result as below:
+---------------------+-----------------------+----------------------+-------------------+--------------------+
| Environment | dpdk_win_llvm_compile | dpdk_mingw64_compile | dpdk_msvc_compile | dpdk_meson_compile |
+=====================+=======================+======================+===================+====================+
| Windows Server 2022 | PEND | PEND | PEND | SKIPPED |
+---------------------+-----------------------+----------------------+-------------------+--------------------+
| FreeBSD 13.4 | SKIPPED | SKIPPED | SKIPPED | PASS |
+---------------------+-----------------------+----------------------+-------------------+--------------------+
| 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.4
Kernel: 13.4-RELEASE-p1
Compiler: clang 18.1.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/31430/
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-10-11 22:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241011094944.3586051-5-tduszynski@marvell.com>
2024-10-11 9:23 ` |SUCCESS| pw145753-145756 [PATCH v14 4/4] eal: add PMU support to tracing library qemudev
2024-10-11 9:27 ` qemudev
2024-10-11 9:52 ` |SUCCESS| pw145756 " checkpatch
2024-10-11 10:43 ` |FAILURE| " 0-day Robot
2024-10-11 22:13 ` dpdklab [this message]
2024-10-11 22:14 ` |SUCCESS| pw145753-145756 [PATCH] [v14,4/4] eal: add PMU support to dpdklab
2024-10-11 22:20 ` dpdklab
2024-10-11 22:23 ` dpdklab
2024-10-11 22:26 ` dpdklab
2024-10-11 22:29 ` dpdklab
2024-10-11 22:30 ` dpdklab
2024-10-11 22:34 ` dpdklab
2024-10-11 22:36 ` dpdklab
2024-10-11 22:36 ` dpdklab
2024-10-11 22:39 ` |PENDING| " dpdklab
2024-10-11 23:12 ` |SUCCESS| " dpdklab
2024-10-12 1:05 ` |PENDING| " dpdklab
2024-10-12 2:04 ` |FAILURE| " dpdklab
2024-10-12 2:09 ` dpdklab
2024-10-12 2:13 ` dpdklab
2024-10-12 2:17 ` 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=6709a2ec.050a0220.fa6c2.a3b5SMTPIN_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).