From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw72433 [PATCH] [v2] mempool/ring: add support for new ring sync modes
Date: Mon, 29 Jun 2020 16:22:41 -0400 (EDT) [thread overview]
Message-ID: <20200629202241.3D5286D437@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2918 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/72433
_Testing PASS_
Submitter: Konstantin Ananyev <konstantin.ananyev@intel.com>
Date: Monday, June 29 2020 16:10:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6248368a9ae1eadf6b7fb05ab37497afdb714429
72433 --> testing pass
Test environment and result as below:
+---------------------+--------------------+-------------------+------------------+----------------+--------------+
| Environment | dpdk_meson_compile | dpdk_compile_spdk | dpdk_compile_ovs | dpdk_unit_test | dpdk_compile |
+=====================+====================+===================+==================+================+==============+
| Windows Server 2019 | PASS | SKIPPED | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+------------------+----------------+--------------+
| Fedora 31 | PASS | PASS | PASS | SKIPPED | PASS |
+---------------------+--------------------+-------------------+------------------+----------------+--------------+
| Ubuntu 18.04 | PASS | PASS | PASS | PASS | PASS |
+---------------------+--------------------+-------------------+------------------+----------------+--------------+
| CentOS 8 | PASS | PASS | PASS | SKIPPED | PASS |
+---------------------+--------------------+-------------------+------------------+----------------+--------------+
| openSUSE Leap 15 | PASS | PASS | PASS | SKIPPED | PASS |
+---------------------+--------------------+-------------------+------------------+----------------+--------------+
| Arch Linux | PASS | SKIPPED | PASS | SKIPPED | PASS |
+---------------------+--------------------+-------------------+------------------+----------------+--------------+
| FreeBSD 11.2 | PASS | PASS | SKIPPED | SKIPPED | PASS |
+---------------------+--------------------+-------------------+------------------+----------------+--------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0
Fedora 31
Kernel: 5.3.16
Compiler: gcc 9.2.1
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
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
Arch Linux
Kernel: latest
Compiler: gcc latest
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/11724/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-06-29 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 20:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-29 20:02 dpdklab
2020-06-29 17:07 dpdklab
2020-06-29 17:06 dpdklab
2020-06-29 16:38 dpdklab
[not found] <20200629161024.29059-1-konstantin.ananyev@intel.com>
2020-06-29 16:11 ` [dpdk-test-report] |SUCCESS| pw72433 [PATCH v2] " 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=20200629202241.3D5286D437@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).