From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144889 [PATCH] net/gve: fix mbuf allocation memory leak
Date: Tue, 01 Oct 2024 19:26:19 -0700 (PDT) [thread overview]
Message-ID: <66fcaf4b.050a0220.1adf3c.a14fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241001234852.3312594-1-joshwash@google.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/144889
_Testing PASS_
Submitter: Joshua Washington <joshwash@google.com>
Date: Tuesday, October 01 2024 23:48:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:aafa5ec4fcb4f9ac166cdbda2b1555f66e9ab188
144889 --> testing pass
Upstream job id: Windows-Compile-DPDK-VS#3281
Test environment and result as below:
+---------------------+-----------------------+----------------------+-------------------+--------------------+
| Environment | dpdk_win_llvm_compile | dpdk_mingw64_compile | dpdk_msvc_compile | dpdk_meson_compile |
+=====================+=======================+======================+===================+====================+
| Windows Server 2022 | PASS | PASS | PASS | SKIPPED |
+---------------------+-----------------------+----------------------+-------------------+--------------------+
| FreeBSD 13.4 | SKIPPED | SKIPPED | SKIPPED | PASS |
+---------------------+-----------------------+----------------------+-------------------+--------------------+
| FreeBSD 14.1 | SKIPPED | SKIPPED | SKIPPED | PASS |
+---------------------+-----------------------+----------------------+-------------------+--------------------+
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/31217/
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-02 2:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241001234852.3312594-1-joshwash@google.com>
2024-10-01 23:33 ` |SUCCESS| pw144889 [PATCH] net/gve: fix mbuf allocation memory leak for DQ Rx qemudev
2024-10-01 23:37 ` qemudev
2024-10-01 23:49 ` checkpatch
2024-10-02 0:44 ` 0-day Robot
2024-10-02 2:11 ` |PENDING| pw144889 [PATCH] net/gve: fix mbuf allocation memory leak dpdklab
2024-10-02 2:18 ` |SUCCESS| " dpdklab
2024-10-02 2:25 ` dpdklab
2024-10-02 2:26 ` dpdklab
2024-10-02 2:26 ` dpdklab [this message]
2024-10-02 2:26 ` |PENDING| " dpdklab
2024-10-02 2:27 ` |SUCCESS| " dpdklab
2024-10-02 2:30 ` dpdklab
2024-10-02 2:37 ` dpdklab
2024-10-02 2:45 ` dpdklab
2024-10-02 2:55 ` |PENDING| " dpdklab
2024-10-02 3:07 ` |SUCCESS| " dpdklab
2024-10-02 4:27 ` dpdklab
2024-10-02 5:09 ` dpdklab
2024-10-02 5:13 ` dpdklab
2024-10-02 5:38 ` dpdklab
2024-10-02 6:20 ` dpdklab
2024-10-02 9:48 ` |PENDING| " dpdklab
2024-10-02 10:09 ` |SUCCESS| " dpdklab
2024-10-02 10:10 ` dpdklab
2024-10-02 10:59 ` dpdklab
2024-10-02 12:49 ` dpdklab
2024-10-02 13:11 ` 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=66fcaf4b.050a0220.1adf3c.a14fSMTPIN_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).