From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147053 [PATCH] eal: support including mapped memory in c
Date: Fri, 25 Oct 2024 20:01:50 -0700 (PDT) [thread overview]
Message-ID: <671c5b9e.630a0220.32b585.6600SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241023231859.1323727-1-kozlyuk@bifit.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147053
_Testing PASS_
Submitter: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Date: Wednesday, October 23 2024 23:18:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:90cb8ff8196f9b9c1c2bcee1c94ea583789bb63f
147053 --> testing pass
Upstream job id: Generic-VM-DPDK-Compile-Meson#30720
Test environment and result as below:
+--------------+--------------------+
| Environment | dpdk_meson_compile |
+==============+====================+
| FreeBSD 13.4 | PASS |
+--------------+--------------------+
FreeBSD 13.4
Kernel: 13.4-RELEASE-p1
Compiler: clang 18.1.6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31631/
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-26 3:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241023231859.1323727-1-kozlyuk@bifit.com>
2024-10-23 22:47 ` |SUCCESS| pw147053 [PATCH] eal: support including mapped memory in core dump qemudev
2024-10-23 22:51 ` qemudev
2024-10-23 23:20 ` checkpatch
2024-10-24 0:27 ` |FAILURE| " 0-day Robot
2024-10-24 3:06 ` |SUCCESS| pw147053 [PATCH] eal: support including mapped memory in c dpdklab
2024-10-24 3:13 ` dpdklab
2024-10-24 3:20 ` dpdklab
2024-10-24 5:02 ` dpdklab
2024-10-24 8:34 ` dpdklab
2024-10-24 23:36 ` dpdklab
2024-10-25 1:01 ` dpdklab
2024-10-25 9:28 ` |PENDING| " dpdklab
2024-10-26 3:01 ` dpdklab [this message]
2024-10-26 4:18 ` |FAILURE| " dpdklab
2024-10-26 4:50 ` 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=671c5b9e.630a0220.32b585.6600SMTPIN_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).