From: dpdklab@iol.unh.edu
To: 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| pw118558 [PATCH] [v2] bus: fix memleak during pci device cleanup
Date: Wed, 19 Oct 2022 12:59:35 -0400 (EDT) [thread overview]
Message-ID: <20221019165935.EC7D319DB7@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/118558
_Functional Testing PASS_
Submitter: Kevin Laatz <kevin.laatz@intel.com>
Date: Wednesday, October 19 2022 12:37:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a74b1b25136a592c275afbfa6b70771469750aee
118558 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/24069/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-10-19 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 16:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-19 20:03 dpdklab
2022-10-19 20:03 dpdklab
2022-10-19 20:01 dpdklab
2022-10-19 19:43 dpdklab
2022-10-19 19:15 dpdklab
2022-10-19 19:14 dpdklab
2022-10-19 19:08 dpdklab
2022-10-19 19:02 dpdklab
2022-10-19 17:26 dpdklab
[not found] <20221019123743.1282969-1-kevin.laatz@intel.com>
2022-10-19 12:36 ` |SUCCESS| pw118558 [PATCH v2] " checkpatch
2022-10-19 13:59 ` 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=20221019165935.EC7D319DB7@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--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).