From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw108260 [PATCH] app/pdump: free mempool at cleanup resources
Date: Thu, 24 Feb 2022 08:40:45 -0500 (EST) [thread overview]
Message-ID: <20220224134045.704496D4C2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/108260
_Functional Testing PASS_
Submitter: Tianli Lai <laitianli@tom.com>
Date: Thursday, February 24 2022 12:52:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ee05a93e1e6633d0fdec409faf09f12a2e05b991
108260 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/21252/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-02-24 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 13:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-25 10:11 dpdklab
2022-02-24 18:05 dpdklab
2022-02-24 17:12 dpdklab
2022-02-24 17:06 dpdklab
2022-02-24 15:11 dpdklab
2022-02-24 14:07 dpdklab
2022-02-24 14:02 dpdklab
2022-02-24 13:55 dpdklab
2022-02-24 13:54 dpdklab
2022-02-24 13:51 dpdklab
2022-02-24 13:45 dpdklab
2022-02-24 13:39 dpdklab
2022-02-24 13:34 dpdklab
[not found] <1645707137-53479-1-git-send-email-laitianli@tom.com>
2022-02-24 12:53 ` checkpatch
2022-02-24 14:38 ` 0-day Robot
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=20220224134045.704496D4C2@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).