From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw72825 [PATCH] [v3, 1/2] eal: fix memory leak when removing event_cb
Date: Sat, 4 Jul 2020 06:01:11 -0400 (EDT) [thread overview]
Message-ID: <20200704100111.18B366D437@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2907 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/72825
_Testing PASS_
Submitter: wangyunjian <wangyunjian@huawei.com>
Date: Thursday, July 02 2020 11:47:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b98447077b0609750c10b84b7b2e7be0c8504fad
72825 --> testing pass
Test environment and result as below:
+---------------------+--------------------+-------------------+--------------+------------------+----------------+
| Environment | dpdk_meson_compile | dpdk_compile_spdk | dpdk_compile | dpdk_compile_ovs | dpdk_unit_test |
+=====================+====================+===================+==============+==================+================+
| Windows Server 2019 | PASS | SKIPPED | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+--------------+------------------+----------------+
| CentOS 8 | PASS | PASS | PASS | PASS | SKIPPED |
+---------------------+--------------------+-------------------+--------------+------------------+----------------+
| openSUSE Leap 15 | PASS | PASS | PASS | PASS | SKIPPED |
+---------------------+--------------------+-------------------+--------------+------------------+----------------+
| Fedora 31 | PASS | PASS | PASS | PASS | SKIPPED |
+---------------------+--------------------+-------------------+--------------+------------------+----------------+
| Arch Linux | PASS | SKIPPED | PASS | PASS | SKIPPED |
+---------------------+--------------------+-------------------+--------------+------------------+----------------+
| Ubuntu 18.04 | PASS | PASS | PASS | PASS | PASS |
+---------------------+--------------------+-------------------+--------------+------------------+----------------+
| FreeBSD 11.2 | PASS | PASS | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+--------------+------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0
CentOS 8
Kernel: 4.18.0.el8_0
Compiler: gcc 8.3.1
openSUSE Leap 15
Kernel: 4.12.14
Compiler: gcc 7.4.1
Fedora 31
Kernel: 5.3.16
Compiler: gcc 9.2.1
Arch Linux
Kernel: latest
Compiler: gcc latest
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/11791/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-07-04 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 10:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-03 10:43 dpdklab
2020-07-02 23:50 dpdklab
2020-07-02 16:39 dpdklab
[not found] <1593690428-12708-1-git-send-email-wangyunjian@huawei.com>
2020-07-02 11:47 ` [dpdk-test-report] |SUCCESS| pw72825 [PATCH v3 " checkpatch
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=20200704100111.18B366D437@noxus.dpdklab.iol.unh.edu \
--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).