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
Subject: |SUCCESS| pw104476 [PATCH] [v1] app/test-gpudev: remove memory leaks in case of errors
Date: Wed, 17 Nov 2021 13:18:41 +0000 (UTC) [thread overview]
Message-ID: <20211117131841.0CD48601B7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/104476
_Functional Testing PASS_
Submitter: Elena Agostini <eagostini@nvidia.com>
Date: Wednesday, November 17 2021 20:44:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:329f73eb355ebd7ca5ff37916d37872d28365452
104476 --> 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/20263/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-11-17 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 13:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-17 16:57 dpdklab
2021-11-17 16:33 dpdklab
2021-11-17 14:05 dpdklab
2021-11-17 13:38 dpdklab
2021-11-17 13:36 dpdklab
2021-11-17 13:32 dpdklab
2021-11-17 13:31 dpdklab
2021-11-17 13:26 dpdklab
2021-11-17 13:24 dpdklab
[not found] <20211117204453.27337-1-eagostini@nvidia.com>
2021-11-17 12:36 ` |SUCCESS| pw104476 [PATCH v1] " checkpatch
2021-11-17 13:18 ` 0-day Robot
2021-11-17 13:10 |SUCCESS| pw104476 [PATCH] [v1] " dpdklab
2021-11-17 13:08 dpdklab
2021-11-17 13:08 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=20211117131841.0CD48601B7@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--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).