From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw67369[v2, 02/13] bbdev: expose device HARQ buffer size at device level
Date: 30 Mar 2020 04:32:47 -0700 [thread overview]
Message-ID: <fecc85$9ohasd@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7159 bytes --]
Test-Label: Intel-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/67369
_Compilation OK_
Submitter: Chautru, Nicolas <nicolas.chautru@intel.com>
Date: 2020-03-30 00:02:49
Reply_mail: 1585526580-113508-3-git-send-email-nicolas.chautru@intel.com
DPDK git baseline: Repo:dpdk-next-crypto, CommitID: 5eb41955211da8e72b28a3c28b49c1a0c7ca283a
Makefile build Summary: 23 Builds Done, 23 Successful, 0 Failures
Meson build Summary: 8 Builds Done, 8 Successful, 0 Failures
+==============================================+===========+==========+
| Makefile | Meson | Document |
+----------------+------+-------+------+------------+-----------+-----------+----------+
| os | gcc | clang | icc | gcc+shared | gcc+debug | gcc/clang | pdf/html |
+----------------+------+-------+------+------------+-----------+-----------+----------+
| RHEL80-64 | pass | | | | | | |
| UB1804-64 | pass | pass | pass | | | pass | pass |
| UB1604-32 | pass | | | | | pass | |
| CENTOS77-64 | pass | pass | pass | pass | pass | pass | |
| UB1604-64 | pass | pass | | | | | |
| WIN10-64 | | | | | | pass | |
| UB1910-64 | pass | | | | | | |
| FC31-64 | pass | pass | | | | pass | |
| CENTOS80-64 | pass | | | | | | |
| FreeBSD1201-64 | pass | pass | | pass | pass | pass | |
| RHEL77-64 | pass | | | | | | |
| SUSE15-64 | pass | pass | | | | pass | |
+----------------+------+-------+------+------------+-----------+-----------+----------+
Test environment and configuration as below:
** Makefile build **
OS: UB1804-64
Kernel Version: 4.15.0-20-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0
Clang Version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-icc
x86_64-native-linuxapp-gcc
OS: UB1604-32
Kernel Version: 4.4.0-131-generic
CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
i686-native-linuxapp-gcc
OS: CENTOS77-64
Kernel Version: 3.10.0-1062.9.1.el7.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc+shared
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc+debug
x86_64-native-linuxapp-icc
OS: UB1604-64
Kernel Version: 4.4.0-176-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609
Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
OS: CENTOS80-64
Kernel Version: 4.18.0-80.11.2.el8_0.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 8.2.1 20180905 (Red Hat 8.2.1-3)
Clang Version: 7.0.1 (tags/RELEASE_701/final)
x86_64-native-linuxapp-gcc
OS: UB1910-64
Kernel Version: 5.3.0-18-generic
CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: gcc (Ubuntu 9.2.1-9ubuntu2) 9.2.1 20191008
Clang Version: 9.0.0-2 (tags/RELEASE_900/final)
x86_64-native-linuxapp-gcc
OS: FC31-64
Kernel Version: 5.3.15-300.fc31.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1)
Clang Version: 9.0.0 (Fedora 9.0.0-1.fc31)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: RHEL80-64
Kernel Version: 4.18.0-80.el8.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 8.2.1 20180905 (Red Hat 8.2.1-3)
Clang Version: 6.0.1 (tags/RELEASE_601/final)
x86_64-native-linuxapp-gcc
OS: FreeBSD1201-64
Kernel Version: 12.1-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.75-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 9.2.0
Clang Version: 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
x86_64-native-bsdapp-gcc+debug
x86_64-native-bsdapp-gcc
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-clang
OS: RHEL77-64
Kernel Version: 3.10.0-1062.9.1.el7.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-gcc
OS: SUSE15-64
Kernel Version: 4.12.14-lp150.11-default
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (SUSE Linux) 7.3.1 20180323 [gcc-7-branch revision 258812]
Clang Version: 5.0.1 (tags/RELEASE_501/final 312548)
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
** Meson build **
OS: UB1804-64
Kernel Version: 4.15.0-20-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
Clang Version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
x86_64-native-linuxapp-doc
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
OS: UB1604-32
OS: CENTOS77-64
Kernel Version: 3.10.0-1062.12.1.el7.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
OS: WIN10-64
Kernel Version: N/A
CPU info: N/A
GCC Version: N/A
Clang Version: Clang 8.0.0
x86_64-windows-clang
OS: FC31-64
Kernel Version: 5.4.18-200.fc31.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1)
Clang Version: 9.0.0 (Fedora 9.0.0-1.fc31)
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
OS: FreeBSD1201-64
Kernel Version: 12.1-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.98-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 9.2.0
Clang Version: 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
OS: SUSE15-64
Kernel Version: 4.12.14-lp150.12.82-default
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (SUSE Linux) 7.4.1 20190905 [gcc-7-branch revision 275407]
Clang Version: 5.0.1 (tags/RELEASE_501/final 312548)
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
DPDK STV team
reply other threads:[~2020-03-30 11:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='fecc85$9ohasd@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--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).